Triple
T4236677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayabusa2 |
E94710
|
entity |
| Predicate | departureFromTargetDate |
P54851
|
FINISHED |
| Object | 2019-11-13 |
—
|
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: 2019-11-13 | Statement: [Hayabusa2, departureFromTargetDate, 2019-11-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureFromTargetDate Context triple: [Hayabusa2, departureFromTargetDate, 2019-11-13]
-
A.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
B.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
-
C.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
D.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
E.
arrivalDatePlanned
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
- F. None of above. chosen
Provenance (4 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e7422a88190955f5f4347fa80d2 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.