Triple
T32746593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA 905 |
E837368
|
entity |
| Predicate | enteredServiceWithNASA |
P78966
|
FINISHED |
| Object | 1974 |
—
|
LITERAL FINISHED |
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: 1974 | Statement: [NASA 905, enteredServiceWithNASA, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredServiceWithNASA Context triple: [NASA 905, enteredServiceWithNASA, 1974]
-
A.
enteredServiceAsAirForceOne
Indicates that an aircraft began official operation in the role designated as Air Force One for transporting the U.S. President.
-
B.
enteredUSServiceAs
Indicates that an entity began serving in an official capacity within the United States (e.g., military, government, or public service) under a specified role or status.
-
C.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
D.
deliveryToNASA
chosen
Indicates the action or arrangement of delivering something to NASA as the receiving organization.
-
E.
roleInRelationToNASA
Indicates that one entity holds a specific role, position, or functional relationship with respect to NASA.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:12 a.m.