Triple
T34353710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna Citation I |
E881654
|
entity |
| Predicate | cabinPressurized |
P22937
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cessna Citation I, cabinPressurized, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinPressurized Context triple: [Cessna Citation I, cabinPressurized, yes]
-
A.
pressurizedCabin
chosen
Indicates that an enclosed space, typically in a vehicle or structure, is maintained at a controlled air pressure different from the outside environment.
-
B.
cabinPressureAltitude
Indicates the altitude corresponding to the current cabin air pressure, as if that pressure were the standard atmospheric pressure at that height.
-
C.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
D.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
-
E.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:58 a.m.