Triple
T17288637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Redstone rocket |
E419721
|
entity |
| Predicate | maximumAltitudeCapability |
P6750
|
FINISHED |
| Object | about 190 km with Mercury capsule |
—
|
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: about 190 km with Mercury capsule | Statement: [Mercury-Redstone rocket, maximumAltitudeCapability, about 190 km with Mercury capsule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAltitudeCapability Context triple: [Mercury-Redstone rocket, maximumAltitudeCapability, about 190 km with Mercury capsule]
-
A.
altitudeCapability
chosen
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
B.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
C.
aircraftHeight
Indicates the vertical distance or altitude of an aircraft relative to a reference level (such as ground or sea level).
-
D.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
E.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43781b7808190a0528ee9c54a0c66 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.