Triple
T12236344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America |
E291601
|
entity |
| Predicate | orbitalRole |
P78410
|
FINISHED |
| Object | lunar orbit support for Apollo 17 |
—
|
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: lunar orbit support for Apollo 17 | Statement: [America, orbitalRole, lunar orbit support for Apollo 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalRole Context triple: [America, orbitalRole, lunar orbit support for Apollo 17]
-
A.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
B.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
C.
orbitalPosition
Indicates the relative location or path of one object in its orbit with respect to a central body or reference frame.
-
D.
spaceSectorRole
chosen
Indicates the functional role or responsibility an entity holds within a specific space sector or domain.
-
E.
roleInApollo
Indicates that an entity holds or held a specific role or position within the Apollo program or an Apollo 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.