Triple
T31665591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Foundation Day |
E808115
|
entity |
| Predicate | dateChange |
P28382
|
FINISHED |
| Object | moved from 8 February to 25 April |
—
|
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: moved from 8 February to 25 April | Statement: [Military Foundation Day, dateChange, moved from 8 February to 25 April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateChange Context triple: [Military Foundation Day, dateChange, moved from 8 February to 25 April]
-
A.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
B.
approximateDateChange
Indicates that the date associated with an entity has changed in an inexact or estimated manner rather than to a precisely known new date.
-
C.
startDateChangedTo
chosen
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
D.
platformChangeDate
Indicates the date on which a platform undergoes or records a change, such as an update, migration, or modification.
-
E.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:59 p.m.