Triple
T4236705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayabusa2 |
E94710
|
entity |
| Predicate | secondTouchdownOnRyuguDate |
P47098
|
FINISHED |
| Object | 2019-07-11 |
—
|
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-07-11 | Statement: [Hayabusa2, secondTouchdownOnRyuguDate, 2019-07-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTouchdownOnRyuguDate Context triple: [Hayabusa2, secondTouchdownOnRyuguDate, 2019-07-11]
-
A.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
B.
secondRoundDate
chosen
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
-
C.
secondApparitionDate
Indicates the date on which an entity appeared or manifested for the second time.
-
D.
secondReachedBy
Indicates that a particular point, state, or entity is reached as the second in order by another entity or process.
-
E.
secondAscentDate
Indicates the date on which the second successful ascent or climb of something (such as a mountain or route) took place.
- 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_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. |
Created at: March 12, 2026, 11:05 p.m.