Triple

T35089742
Position Surface form Disambiguated ID Type / Status
Subject Indian Springs State Park E1012683 entity
Predicate hasWaterBody P165 FINISHED
Object Big Sandy Creek
Big Sandy Creek is a natural waterway flowing through Indian Springs State Park in Georgia, contributing to the park’s scenic landscape and recreational opportunities.
E2148440 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: Big Sandy Creek | Statement: [Indian Springs State Park, hasWaterBody, Big Sandy Creek]
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: Big Sandy Creek
Triple: [Indian Springs State Park, hasWaterBody, Big Sandy Creek]
Generated description
Big Sandy Creek is a natural waterway flowing through Indian Springs State Park in Georgia, contributing to the park’s scenic landscape and recreational opportunities.

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_69f76dd432ec8190969bc32acfc152b1 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78bdaede0819086c38632ba4257c9 completed May 3, 2026, 5:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a385bba10f08190a4c27ba98e496a93 completed June 21, 2026, 9:46 p.m.
NEDg Description generation batch_6a385cd2f1248190a26ee3bdc77db301 completed June 21, 2026, 9:51 p.m.
NED2 Entity disambiguation (via description) batch_6a3860e6f4c48190bc96b1c4d289e650 completed June 21, 2026, 10:08 p.m.
Created at: May 3, 2026, 4:01 p.m.