Triple
T670660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces Movement |
E12962
|
entity |
| Predicate | dateOfMajorEvent |
P925
|
FINISHED |
| Object | 25 April 1974 |
—
|
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: 25 April 1974 | Statement: [Armed Forces Movement, dateOfMajorEvent, 25 April 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMajorEvent Context triple: [Armed Forces Movement, dateOfMajorEvent, 25 April 1974]
-
A.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.