Triple
T1533026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American P-51 Mustang |
E32486
|
entity |
| Predicate | climbRate |
P21969
|
FINISHED |
| Object | about 3,200 ft/min (16.3 m/s) for P-51D |
—
|
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 3,200 ft/min (16.3 m/s) for P-51D | Statement: [North American P-51 Mustang, climbRate, about 3,200 ft/min (16.3 m/s) for P-51D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbRate Context triple: [North American P-51 Mustang, climbRate, about 3,200 ft/min (16.3 m/s) for P-51D]
-
A.
rateOfClimb
chosen
Indicates the vertical speed at which an entity ascends or descends over time.
-
B.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
C.
climbingMechanism
Indicates a mechanism or method by which an entity ascends or climbs another surface or structure.
-
D.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
E.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a915f323bc8190aa757142c225e0ae |
completed | March 5, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69a907b046448190be8ea4d7b20255f7 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.