Triple
T11000302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus laboratory |
E259985
|
entity |
| Predicate | firstActivationOnISS |
P96571
|
FINISHED |
| Object | 2008-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: 2008-02 | Statement: [Columbus laboratory, firstActivationOnISS, 2008-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstActivationOnISS Context triple: [Columbus laboratory, firstActivationOnISS, 2008-02]
-
A.
firstDockingWithISS
Indicates that an object or mission represents the initial time a spacecraft docks with the International Space Station.
-
B.
firstISSMission
Indicates that the subject entity represents the first mission associated with the International Space Station (ISS) for the given context.
-
C.
firstUseInOrbit
Indicates that this is the first time the object or system is being used while in orbit.
-
D.
firstISSRendezvous
Indicates that the event represents the first successful rendezvous (meeting or docking) with the International Space Station for the entities involved.
-
E.
firstUSRoverOnMars
Indicates that the subject is the first U.S. rover to successfully land and operate on Mars.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d5457c819096630246fa5f7076 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.