Triple
T9285965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas frontier |
E223394
|
entity |
| Predicate | sawConflictBetween |
P4897
|
FINISHED |
| Object | Anglo-American settlers |
—
|
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: Anglo-American settlers | Statement: [Texas frontier, sawConflictBetween, Anglo-American settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawConflictBetween Context triple: [Texas frontier, sawConflictBetween, Anglo-American settlers]
-
A.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
B.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
C.
conflictWith
chosen
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
D.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
-
E.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0821b1108190b16e9570b09a14de |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.