Triple
T33766356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna Citation Encore |
E865239
|
entity |
| Predicate | hasAirstairDoor |
P177667
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cessna Citation Encore, hasAirstairDoor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirstairDoor Context triple: [Cessna Citation Encore, hasAirstairDoor, true]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
C.
hasDomeOrRoofAccess
Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
-
D.
hasStageDoor
Indicates that a venue or building possesses a dedicated stage door used for performers and staff to access backstage areas.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:45 a.m.