Triple

T26743116
Position Surface form Disambiguated ID Type / Status
Subject Jackson County, Oklahoma E674319 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Olustee, Oklahoma
Olustee, Oklahoma is a small rural town in southwestern Oklahoma known for its agricultural community and location within Jackson County.
E1803858 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: Olustee, Oklahoma | Statement: [Jackson County, Oklahoma, hasJurisdictionOver, Olustee, Oklahoma]
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: Olustee, Oklahoma
Triple: [Jackson County, Oklahoma, hasJurisdictionOver, Olustee, Oklahoma]
Generated description
Olustee, Oklahoma is a small rural town in southwestern Oklahoma known for its agricultural community and location within 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_69eecda63a3881908095c47900692e65 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f61880cac881909ed6b653b09164d2 completed May 2, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c8d3bf0c8190a1e6c299f65fb1be completed May 26, 2026, 4:22 p.m.
NEDg Description generation batch_6a15ca33a1108190895682956756c2f1 completed May 26, 2026, 4:28 p.m.
NED2 Entity disambiguation (via description) batch_6a15caa74e9c8190ad43be1d8ed6ad15 completed May 26, 2026, 4:30 p.m.
Created at: April 27, 2026, 3:50 a.m.