Triple
T4118254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratolaunch carrier aircraft |
E90345
|
entity |
| Predicate | takeoffWeightClass |
P54377
|
FINISHED |
| Object | very heavy aircraft |
—
|
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: very heavy aircraft | Statement: [Stratolaunch carrier aircraft, takeoffWeightClass, very heavy aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffWeightClass Context triple: [Stratolaunch carrier aircraft, takeoffWeightClass, very heavy aircraft]
-
A.
takeoffWeightOnRecordFlight
Indicates the recorded takeoff weight associated with a specific flight.
-
B.
maximumTakeoffWeight
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
C.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
D.
takeoffMethod
Indicates the method or procedure by which an aircraft or object initiates its takeoff from a surface or launch point.
-
E.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.