Triple
T10787915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSM-103 |
E254494
|
entity |
| Predicate | spacecraftSection |
P37024
|
FINISHED |
| Object | command module |
—
|
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: command module | Statement: [CSM-103, spacecraftSection, command module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftSection Context triple: [CSM-103, spacecraftSection, command module]
-
A.
spacecraft
Indicates that an entity is a vehicle or object designed to travel or operate in outer space.
-
B.
spacecraftComponents
chosen
Indicates that one entity is a spacecraft and the other is a component or part that belongs to or is used in that spacecraft.
-
C.
spacecraftModel
Indicates that one entity is the specific model or design type of a spacecraft associated with another entity.
-
D.
spaceSegment
Indicates that one entity is a space-based component or portion of a larger system or infrastructure associated with the other entity.
-
E.
featuresSpacecraft
Indicates that one entity includes, presents, or prominently involves a spacecraft as part of its content, composition, or subject matter.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.