Triple

T23945403
Position Surface form Disambiguated ID Type / Status
Subject Pike Township, Marion County, Indiana E602897 entity
Predicate containsNeighborhood P4813 FINISHED
Object Augusta, Indiana
Augusta, Indiana is a small residential neighborhood located within Pike Township on the northwest side of Indianapolis.
E1643493 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: Augusta, Indiana | Statement: [Pike Township, Marion County, Indiana, containsNeighborhood, Augusta, Indiana]
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: Augusta, Indiana
Triple: [Pike Township, Marion County, Indiana, containsNeighborhood, Augusta, Indiana]
Generated description
Augusta, Indiana is a small residential neighborhood located within Pike Township on the northwest side of Indianapolis.

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_69e2953e4924819093f1c24c03476b42 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d02dd0cc8190b32eb86bdfe0bf9a completed April 29, 2026, 9:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10044f67548190a004cb281c839ac5 completed May 22, 2026, 7:22 a.m.
NEDg Description generation batch_6a10056bde0c8190938cf666993e6f70 completed May 22, 2026, 7:27 a.m.
NED2 Entity disambiguation (via description) batch_6a1006162a308190a1c1ed715d0a6691 completed May 22, 2026, 7:30 a.m.
Created at: April 17, 2026, 9:11 p.m.