Triple
T29657597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Doklam standoff |
E750312
|
entity |
| Predicate | sparkedBy |
P693
|
FINISHED |
| Object | Chinese road construction in Doklam |
—
|
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: Chinese road construction in Doklam | Statement: [2017 Doklam standoff, sparkedBy, Chinese road construction in Doklam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sparkedBy Context triple: [2017 Doklam standoff, sparkedBy, Chinese road construction in Doklam]
-
A.
firedBy
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
B.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
inducedBy
Indicates that one entity is the cause, source, or triggering factor that brings about the existence, occurrence, or state of another entity.
-
D.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
E.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f2939608190b987081b44b2fefd |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:56 p.m.