Triple
T36360903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will Rogers Country Centennial Trail |
E895488
|
entity |
| Predicate | namedForBirthPlace |
P98931
|
FINISHED |
| Object | Oologah, Oklahoma |
—
|
NE NERFINISHED |
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: Oologah, Oklahoma | Statement: [Will Rogers Country Centennial Trail, namedForBirthPlace, Oologah, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForBirthPlace Context triple: [Will Rogers Country Centennial Trail, namedForBirthPlace, Oologah, Oklahoma]
-
A.
namedAfterBirthPlace
chosen
Indicates that an entity is given a name derived from or based on the place where it was born.
-
B.
namedForPersonBornInArea
Indicates that something is named after a person who was born in the specified geographic area.
-
C.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
D.
namedForPersonBirthplaceState
Indicates that something is named after a person, specifically using the state where that person was born as the basis for the name.
-
E.
placeOfBirth
Indicates the location where a person or other entity was born.
- F. None of above.
Provenance (3 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:09 p.m.