Triple
T25563506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNTAES |
E640775
|
entity |
| Predicate | startOfMission |
P14315
|
FINISHED |
| Object | 1996-01 |
—
|
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: 1996-01 | Statement: [UNTAES, startOfMission, 1996-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfMission Context triple: [UNTAES, startOfMission, 1996-01]
-
A.
missionStart
chosen
Indicates the point in time or event at which a mission or task officially begins.
-
B.
launchOnMission
Indicates initiating the sending of an entity (typically a vehicle, spacecraft, or device) to carry out a specific mission or operation.
-
C.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
D.
surfaceMissionStart
Indicates the point in time or event when a mission or operation on a surface (such as a planetary or lunar surface) begins.
-
E.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 3:47 p.m.