Triple
T36987133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-204 |
E914994
|
entity |
| Predicate | missionPayload |
P191130
|
FINISHED |
| Object | Apollo Lunar Module test article LM-1 |
—
|
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 Lunar Module test article LM-1 | Statement: [SA-204, missionPayload, Apollo Lunar Module test article LM-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPayload Context triple: [SA-204, missionPayload, Apollo Lunar Module test article LM-1]
-
A.
cargoMission
Indicates a mission whose primary purpose is to transport cargo from one location to another.
-
B.
missionBody
Indicates that an entity serves as the physical or organizational body responsible for carrying out or hosting a particular mission.
-
C.
missionPatch
Indicates that an entity serves as the official emblem or insignia associated with a particular mission.
-
D.
missionTypeSupport
Indicates that one entity provides support or assistance to another within the context of a specific mission or operation.
-
E.
missionID
Indicates a unique identifier that associates an entity with a specific mission or operation.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.