Triple
T33901280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 Command and Service Module |
E869052
|
entity |
| Predicate | carriedLifeSupportSystems |
P64179
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apollo 15 Command and Service Module, carriedLifeSupportSystems, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedLifeSupportSystems Context triple: [Apollo 15 Command and Service Module, carriedLifeSupportSystems, yes]
-
A.
crewLifeSupportCapability
chosen
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
B.
crewEquipment
Indicates that certain equipment is assigned to, used by, or associated with a specific crew.
-
C.
rescueEquipment
Indicates that one entity serves as equipment or gear used by another entity for performing rescue or emergency-saving operations.
-
D.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
E.
carriedPersonnelType
Indicates the type or category of personnel that are transported or carried by 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.