Triple
T33901275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 Command and Service Module |
E869052
|
entity |
| Predicate | serviceModuleEngineType |
P192445
|
FINISHED |
| Object | AJ10-137 |
—
|
NE NERFINISHED |
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: AJ10-137 | Statement: [Apollo 15 Command and Service Module, serviceModuleEngineType, AJ10-137]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceModuleEngineType Context triple: [Apollo 15 Command and Service Module, serviceModuleEngineType, AJ10-137]
-
A.
serviceModuleType
Indicates the type or category of a service module associated with an entity or system.
-
B.
serviceProviderType
Indicates the category or kind of service provider associated with an entity or transaction.
-
C.
serviceBundleType
Indicates the classification or category of a service bundle that specifies what kind of grouped services it represents.
-
D.
serviceModuleCompanion
Indicates that one module functions as a supporting or companion service module to another module.
-
E.
serviceModuleShape
Indicates the geometric configuration or physical form that characterizes a service module.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: May 1, 2026, 1:48 a.m.