Triple
T35689537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLSS control panel |
E1031250
|
entity |
| Predicate | missionExamples |
P83603
|
FINISHED |
| Object | Apollo 11 EVAs |
—
|
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 11 EVAs | Statement: [PLSS control panel, missionExamples, Apollo 11 EVAs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionExamples Context triple: [PLSS control panel, missionExamples, Apollo 11 EVAs]
-
A.
missionOnEarth
Indicates that an entity has a mission, assignment, or purpose specifically taking place on Earth.
-
B.
exampleMission
chosen
Indicates that one entity serves as a representative or illustrative mission associated with another entity.
-
C.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
D.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
E.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:05 p.m.