Triple
T18912577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Space Station |
E462643
|
entity |
| Predicate | firstLongDurationCrewArrival |
P64928
|
FINISHED |
| Object | 2000-11-02 |
—
|
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: 2000-11-02 | Statement: [International Space Station, firstLongDurationCrewArrival, 2000-11-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLongDurationCrewArrival Context triple: [International Space Station, firstLongDurationCrewArrival, 2000-11-02]
-
A.
crewLandingDuration
Indicates the length of time a crewed mission spends on the surface after landing before departure or ascent.
-
B.
firstCrewBoarded
chosen
Indicates that the initial group of crew members has boarded or entered a specified vehicle, vessel, or location.
-
C.
arrivalByShip
Indicates that an entity reaches a destination specifically by traveling on a ship.
-
D.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
E.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c624516c81909e6bf04707d3c71c |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.