Triple
T35806623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Red |
E1035116
|
entity |
| Predicate | appearedInTerritorySystem |
P196965
|
FINISHED |
| Object | Texas wrestling territory |
—
|
LITERAL 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: Texas wrestling territory | Statement: [Texas Red, appearedInTerritorySystem, Texas wrestling territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearedInTerritorySystem Context triple: [Texas Red, appearedInTerritorySystem, Texas wrestling territory]
-
A.
territorySystem
Indicates a relationship where a territory is governed, organized, or managed under a particular administrative or political system.
-
B.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
E.
usedAsTerritoryFrom
Indicates that an entity served as a territory for another entity starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 3, 2026, 4:06 p.m.