Triple
T34117444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna Citation Longitude |
E875010
|
entity |
| Predicate | maximumTakeoffWeightPounds |
P10870
|
FINISHED |
| Object | approximately 39450 |
—
|
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: approximately 39450 | Statement: [Cessna Citation Longitude, maximumTakeoffWeightPounds, approximately 39450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTakeoffWeightPounds Context triple: [Cessna Citation Longitude, maximumTakeoffWeightPounds, approximately 39450]
-
A.
maximumTakeoffWeight
chosen
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
B.
maximumLandingWeight
Indicates the greatest allowable weight at which an aircraft is certified to land.
-
C.
designedTakeoffWeight_tonnes
Indicates the aircraft’s intended maximum takeoff weight, measured in metric tonnes, as specified in its design.
-
D.
takeoffWeightClass
Indicates the classification of an aircraft or vehicle based on its weight at the time of takeoff.
-
E.
takeoffWeightOnRecordFlight
Indicates the recorded takeoff weight associated with a specific flight.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:53 a.m.