Triple
T36660079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 14 Command and Service Module |
E905094
|
entity |
| Predicate | crewOperations |
P186129
|
FINISHED |
| Object | navigation and guidance |
—
|
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: navigation and guidance | Statement: [Apollo 14 Command and Service Module, crewOperations, navigation and guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewOperations Context triple: [Apollo 14 Command and Service Module, crewOperations, navigation and guidance]
-
A.
crewOperated
Indicates that an entity is operated or controlled by a crew rather than autonomously or individually.
-
B.
crewChief
Indicates that one person serves as the lead or supervising crew chief responsible for directing and managing another person or group in an operational context.
-
C.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
D.
crewControls
Indicates that a crew has authority over, manages, or directs the operation or behavior of another entity.
-
E.
crewStatus
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.