Triple
T17359450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 25143 Itokawa |
E422028
|
entity |
| Predicate | sampleReturnArrivalOnEarth |
P37335
|
FINISHED |
| Object | 2010-06-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: 2010-06-13 | Statement: [25143 Itokawa, sampleReturnArrivalOnEarth, 2010-06-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleReturnArrivalOnEarth Context triple: [25143 Itokawa, sampleReturnArrivalOnEarth, 2010-06-13]
-
A.
returnToEarthDateUTC
chosen
Indicates the date and time, in Coordinated Universal Time (UTC), when something or someone is scheduled or expected to return to Earth.
-
B.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
C.
transportedToEarthBy
Indicates that an entity was moved or carried from another location or context to Earth by a specified agent or means.
-
D.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
-
E.
spaceStationReentryLocation
Indicates the geographic location where a space station (or its remnants) reenters the Earth's atmosphere.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.