Triple
T32256586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion 38 |
E824041
|
entity |
| Predicate | stageNumberOnPegasusXL |
P174449
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Orion 38, stageNumberOnPegasusXL, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageNumberOnPegasusXL Context triple: [Orion 38, stageNumberOnPegasusXL, 3]
-
A.
stageNumber
Indicates the specific sequential position or order of a stage within a multi-stage process or structure.
-
B.
stageNumberOnSaturnV
Indicates the specific numbered stage position that a component or element occupies on the Saturn V launch vehicle.
-
C.
stageNumberOnSaturnIB
Indicates the specific stage number assigned to a component of the Saturn IB launch vehicle.
-
D.
hasPylonCount
Indicates the relationship specifying how many pylons are associated with or present in a given entity.
-
E.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
- F. None of above. chosen
Provenance (4 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:41 a.m.