Triple
T2139048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadarm |
E46718
|
entity |
| Predicate | usedForMission |
P98
|
FINISHED |
| Object | International Space Station assembly |
—
|
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: International Space Station assembly | Statement: [Canadarm, usedForMission, International Space Station assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForMission Context triple: [Canadarm, usedForMission, International Space Station assembly]
-
A.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
-
D.
usedWhenOnBoard
Indicates that something is employed or utilized while a person or object is on board a vehicle, vessel, or similar conveyance.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.