Triple
T4236704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayabusa2 |
E94710
|
entity |
| Predicate | firstTouchdownOnRyuguDate |
P54855
|
FINISHED |
| Object | 2019-02-22 |
—
|
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-02-22 | Statement: [Hayabusa2, firstTouchdownOnRyuguDate, 2019-02-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTouchdownOnRyuguDate Context triple: [Hayabusa2, firstTouchdownOnRyuguDate, 2019-02-22]
-
A.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
B.
firstShotsFiredOn
Indicates that the referenced event or entity marks the initial occurrence of shots being fired on a specified date, time, or occasion.
-
C.
firstSuccessfulImpactBy
Indicates that one entity is the earliest or initial successful impactor upon another entity in a given context or sequence of events.
-
D.
firstFlownAt
Indicates the date or time at which something (typically an aircraft or spacecraft) was first flown.
-
E.
firstSuccessfulICBMFlightDate
Indicates the calendar date on which an entity’s first successful intercontinental ballistic missile (ICBM) flight test occurred.
- 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.