Triple

T31149028
Position Surface form Disambiguated ID Type / Status
Subject Unadilla, New York E794015 entity
Predicate namedAfter P63 FINISHED
Object Unadilla River
The Unadilla River is a tributary in central New York that forms part of the boundary between the Catskill and Appalachian regions before joining the Susquehanna River.
 E2015277 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: Unadilla River | Statement: [Unadilla, New York, namedAfter, Unadilla 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: Unadilla River
Triple: [Unadilla, New York, namedAfter, Unadilla River]
Generated description
The Unadilla River is a tributary in central New York that forms part of the boundary between the Catskill and Appalachian regions before joining the Susquehanna River.

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_69f224d41bb48190a5621cd1485e3a30 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f697ed73f08190b1bca40fa96e6f61 completed May 3, 2026, 12:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3485e732e88190b2ab98a31a1d5daa completed June 18, 2026, 11:57 p.m.
NEDg Description generation batch_6a3486c2afa881909c2af63e7d642668 completed June 19, 2026, 12:01 a.m.
NED2 Entity disambiguation (via description) batch_6a34895926748190b5a5b5e82f4944fc completed June 19, 2026, 12:12 a.m.
Created at: April 29, 2026, 9:06 p.m.