Triple
T34901707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawnee, Oklahoma |
E1006607
|
entity |
| Predicate | isHistoricHomeAreaFor |
P136261
|
FINISHED |
| Object | Absentee Shawnee Tribe |
—
|
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: Absentee Shawnee Tribe | Statement: [Shawnee, Oklahoma, isHistoricHomeAreaFor, Absentee Shawnee Tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricHomeAreaFor Context triple: [Shawnee, Oklahoma, isHistoricHomeAreaFor, Absentee Shawnee Tribe]
-
A.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
B.
isHistoricRegionFor
chosen
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
C.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
D.
isHistoricDistrict
Indicates that an area has been officially recognized or designated as a historic district due to its historical, cultural, or architectural significance.
-
E.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.