Triple
T2094990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coahuila y Tejas |
E32759
|
entity |
| Predicate | lostTerritoryThrough |
P21277
|
FINISHED |
| Object | Texas independence |
—
|
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 independence | Statement: [Coahuila y Tejas, lostTerritoryThrough, Texas independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostTerritoryThrough Context triple: [Coahuila y Tejas, lostTerritoryThrough, Texas independence]
-
A.
lostContinentalTerritory
Indicates that one entity has lost control over part or all of its mainland territorial holdings to another entity or as a result of some event.
-
B.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
C.
territorialConsequence
chosen
Indicates the resulting change or effect on territorial control, boundaries, or status that follows from a particular event, action, or condition.
-
D.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
E.
countryCedingTerritory
Indicates that one country is formally transferring control or ownership of a portion of its territory to another entity.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba99ddc48190bb2097b56efb7aca |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.