Triple
T15138620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 Command Module Columbia |
E361622
|
entity |
| Predicate | commandModuleMass |
P53671
|
FINISHED |
| Object | about 5,560 kg |
—
|
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: about 5,560 kg | Statement: [Apollo 11 Command Module Columbia, commandModuleMass, about 5,560 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandModuleMass Context triple: [Apollo 11 Command Module Columbia, commandModuleMass, about 5,560 kg]
-
A.
landingModuleMass
Indicates the mass of a landing module involved in a landing operation or configuration.
-
B.
spacecraftMass
chosen
Indicates the mass value associated with a spacecraft in a given context.
-
C.
missionCommandModule
Indicates that one entity serves as the command module component of a mission involving the other entity.
-
D.
commandModulePilot
Indicates that an entity serves as the pilot of a command module in a space mission or spacecraft system.
-
E.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b59b488190b0016970647e7483 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.