Triple
T9461970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Gandamak |
E228168
|
entity |
| Predicate | endedConflictPhase |
P89075
|
FINISHED |
| Object | early phase of the Second Anglo-Afghan War |
—
|
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: early phase of the Second Anglo-Afghan War | Statement: [Treaty of Gandamak, endedConflictPhase, early phase of the Second Anglo-Afghan War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedConflictPhase Context triple: [Treaty of Gandamak, endedConflictPhase, early phase of the Second Anglo-Afghan War]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
statusDuringConflict
Indicates the role, condition, or standing an entity held throughout a specified conflict or period of hostilities.
-
C.
followsConflictPhase
Indicates that one conflict phase occurs after and is temporally subsequent to another conflict phase.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcc8b1881908aa6ee13ab195330 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69ccbf9b080c819098934a18cf2bac5d |
completed | April 1, 2026, 6:47 a.m. |
Created at: March 30, 2026, 7:53 p.m.