Triple
T32279963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo spacecraft CSM-111 |
E824661
|
entity |
| Predicate | crewTransportFor |
P11822
|
FINISHED |
| Object | Thomas P. Stafford |
—
|
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: Thomas P. Stafford | Statement: [Apollo spacecraft CSM-111, crewTransportFor, Thomas P. Stafford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransportFor Context triple: [Apollo spacecraft CSM-111, crewTransportFor, Thomas P. Stafford]
-
A.
crewTransportSegment
Indicates a segment of a journey during which crew members are transported from one location to another.
-
B.
transportFor
chosen
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
C.
intendedCrewVehicle
Indicates that a particular vehicle is designated or planned to be used by a specific crew.
-
D.
carriesCrewOf
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc7edfc81909d0008fa9364de54 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.