Triple

T33242145
Position Surface form Disambiguated ID Type / Status
Subject Historic London Town and Gardens E850991 entity
Predicate locatedOnWaterbody P1489 FINISHED
Object South River
South River is a tidal tributary of the Chesapeake Bay in Maryland, known for bordering historic sites and waterfront communities near Annapolis.
E224251 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: South River | Statement: [Historic London Town and Gardens, locatedOnWaterbody, South River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: South River
Triple: [Historic London Town and Gardens, locatedOnWaterbody, South River]
Generated description
South River is a tidal tributary of the Chesapeake Bay in Maryland, known for bordering historic sites and waterfront communities near Annapolis.

Provenance (5 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f34962386c81909ddc3bf9e18ddeb8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6daf0cd708190ab344d594aad93cc completed May 3, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a363c76304081909d4a3222bbc3b569 completed June 20, 2026, 7:08 a.m.
NEDg Description generation batch_6a364858b6e4819098839767b3fbfda4 completed June 20, 2026, 7:59 a.m.
NED2 Entity disambiguation (via description) batch_6a3648df22f8819081e405f644f602c9 completed June 20, 2026, 8:01 a.m.
Created at: May 1, 2026, 1:31 a.m.