Triple
T32184017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Sill Apache Tribe |
E822057
|
entity |
| Predicate | hasGovernmentBasedIn |
P21613
|
FINISHED |
| Object | 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: Oklahoma | Statement: [Fort Sill Apache Tribe, hasGovernmentBasedIn, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentBasedIn Context triple: [Fort Sill Apache Tribe, hasGovernmentBasedIn, Oklahoma]
-
A.
basedInCapital
Indicates that an entity is located or has its main base of operations in a capital city.
-
B.
hasSeatOfAdministration
chosen
Indicates that an administrative body or jurisdiction has a specific place or location that serves as its central seat of governance or administration.
-
C.
governingCountryCapitalLocatedIn
Indicates that the capital city of a governing country is geographically located within a specified territory or region.
-
D.
countryOfSeat
Indicates the country in which an organization’s official seat, headquarters, or principal office is located.
-
E.
capitalOfGoverningCountry
Indicates that a city serves as the capital of the country that governs a given territory or region.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab75a948190a531ac204aee4fca |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:34 a.m.