Triple
T24256192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo CSM-118 |
E603674
|
entity |
| Predicate | crewTransportMissionNumber |
P26361
|
FINISHED |
| Object | third Skylab crewed mission |
—
|
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: third Skylab crewed mission | Statement: [Apollo CSM-118, crewTransportMissionNumber, third Skylab crewed mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransportMissionNumber Context triple: [Apollo CSM-118, crewTransportMissionNumber, third Skylab crewed mission]
-
A.
missionNumber
chosen
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
-
B.
volareMissionAssociatedWith
Indicates that a Volare mission is linked or connected to another entity through an association or involvement relationship.
-
C.
numberOfMissions
Indicates the total count of missions associated with a given entity or context.
-
D.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
E.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6284dc8190a357f15d95b0360a |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.