Triple
T36572375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS New Orleans (LPH-11) |
E902153
|
entity |
| Predicate | NASARecoveryMission |
P67369
|
FINISHED |
| Object | Apollo 14 |
—
|
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 14 | Statement: [USS New Orleans (LPH-11), NASARecoveryMission, Apollo 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NASARecoveryMission Context triple: [USS New Orleans (LPH-11), NASARecoveryMission, Apollo 14]
-
A.
spacecraftRecoveryBy
chosen
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
B.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
C.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
D.
spaceProgram
Indicates that an entity is involved in, operates, or is associated with an organized program dedicated to space exploration, research, or related activities.
-
E.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.