Triple

T23218511
Position Surface form Disambiguated ID Type / Status
Subject Tuckasegee River E580816 entity
Predicate hasNameVariant P457 FINISHED
Object Tuckaseigee River
The Tuckaseigee River is a mountain river in western North Carolina known for its scenic beauty, whitewater recreation, and role in draining much of Jackson County.
E1633468 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: Tuckaseigee River | Statement: [Tuckasegee River, hasNameVariant, Tuckaseigee 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: Tuckaseigee River
Triple: [Tuckasegee River, hasNameVariant, Tuckaseigee River]
Generated description
The Tuckaseigee River is a mountain river in western North Carolina known for its scenic beauty, whitewater recreation, and role in draining much of Jackson County.

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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916653f08190a7dcbc659c6b6a25 completed April 29, 2026, 5:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe32d10c88190b3b25f6768910b2d completed May 22, 2026, 5:01 a.m.
NEDg Description generation batch_6a0fe406801c819082d404e74b5ae415 completed May 22, 2026, 5:05 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe4aa1dd881909820b5fe92608d6f completed May 22, 2026, 5:07 a.m.
Created at: April 17, 2026, 4:08 p.m.