Triple
T23679032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Module 017 |
E584965
|
entity |
| Predicate | associatedMissionNumber |
P26361
|
FINISHED |
| Object | Apollo 4 (AS-501) |
—
|
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: Apollo 4 (AS-501) | Statement: [Service Module 017, associatedMissionNumber, Apollo 4 (AS-501)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMissionNumber Context triple: [Service Module 017, associatedMissionNumber, Apollo 4 (AS-501)]
-
A.
relatedMission
Indicates that one mission is connected or associated with another mission in a meaningful way, such as by shared goals, context, participants, or timeline.
-
B.
missionNumber
chosen
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
-
C.
associatedShuttleMission
Indicates that there is a relationship linking something (e.g., an object, event, or record) to a specific space shuttle mission with which it is connected or involved.
-
D.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
E.
numberOfMissions
Indicates the total count of missions associated with a given entity or context.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f5a7b48190b93d27416003e173 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.