Triple
T32311060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Indian Springs (1825) |
E825499
|
entity |
| Predicate | causeOfTensionWith |
P61068
|
FINISHED |
| Object | Creek traditionalist leaders |
—
|
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: Creek traditionalist leaders | Statement: [Treaty of Indian Springs (1825), causeOfTensionWith, Creek traditionalist leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfTensionWith Context triple: [Treaty of Indian Springs (1825), causeOfTensionWith, Creek traditionalist leaders]
-
A.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
B.
hasCauseOfConflict
chosen
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
-
C.
relationshipConflictWith
Indicates a state of opposition, disagreement, or incompatibility between two entities within a relationship.
-
D.
hasTypeOfTension
Indicates that one entity is associated with, or characterized by, a specific kind or category of tension.
-
E.
tensionSource
Indicates that one entity is the origin or cause of tension affecting another entity or situation.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:46 a.m.