Triple
T15138621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 Command Module Columbia |
E361622
|
entity |
| Predicate | serviceModuleMass |
P117467
|
FINISHED |
| Object | about 24,520 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 24,520 kg | Statement: [Apollo 11 Command Module Columbia, serviceModuleMass, about 24,520 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceModuleMass Context triple: [Apollo 11 Command Module Columbia, serviceModuleMass, about 24,520 kg]
-
A.
serviceModuleFunction
Indicates that a function is provided or performed by a specific service module within a system.
-
B.
serviceModuleCompanion
Indicates that one module functions as a supporting or companion service module to another module.
-
C.
serviceModuleOrigin
Indicates the original source or provider from which a service module is derived or obtained.
-
D.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:07 a.m.