Triple
T24428427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Military Group |
E615924
|
entity |
| Predicate | timeInPowerApproximateStart |
P45811
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [New Military Group, timeInPowerApproximateStart, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInPowerApproximateStart Context triple: [New Military Group, timeInPowerApproximateStart, 1979]
-
A.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
B.
startTimeAsRulingParty
Indicates the point in time when an entity begins its tenure or role as the ruling party.
-
C.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
D.
governingSince
chosen
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
E.
statePowerStartDate
Indicates the date on which a state or governing authority first began to exercise its official power or jurisdiction.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.