Triple
T33731961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block II Command and Service Module |
E864295
|
entity |
| Predicate | commandModuleShape |
P193145
|
FINISHED |
| Object | blunt‑body conical capsule |
—
|
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: blunt‑body conical capsule | Statement: [Block II Command and Service Module, commandModuleShape, blunt‑body conical capsule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandModuleShape Context triple: [Block II Command and Service Module, commandModuleShape, blunt‑body conical capsule]
-
A.
commandModuleType
Indicates the specific type or category assigned to a command module within a system or architecture.
-
B.
commandModuleFunction
Indicates that an entity serves as a command module and specifies the function or role that this command module performs.
-
C.
controllerShape
Indicates that one entity has the specified geometric or physical form used as a controller in an interaction or system.
-
D.
commandModuleName
Indicates the name assigned to a specific command module within a system or application.
-
E.
commandModulePilot
Indicates that an entity serves as the pilot of a command module in a space mission or spacecraft system.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 1, 2026, 1:44 a.m.