Triple
T9606028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Resistance Movement |
E231973
|
entity |
| Predicate | governsSince |
P45811
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [National Resistance Movement, governsSince, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsSince Context triple: [National Resistance Movement, governsSince, 1986]
-
A.
governingSince
chosen
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
B.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
C.
governmentInPowerAtEnactment
Indicates that a specific government or administration was the one holding power at the time a particular law, policy, or measure was enacted.
-
D.
governedByAtTimeOfEvent
Indicates that an entity is under the authority or control of a particular governing agent specifically at the time a given event occurs.
-
E.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a6006d48190adc03306533b9be6 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.