Triple
T33674732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna Citation Ultra |
E862726
|
entity |
| Predicate | numberOfPilotsRequired |
P89118
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Cessna Citation Ultra, numberOfPilotsRequired, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPilotsRequired Context triple: [Cessna Citation Ultra, numberOfPilotsRequired, 2]
-
A.
numberOfPilotsInDisplay
Indicates the total count of pilots participating in a particular display or demonstration event.
-
B.
crewRequired
chosen
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
C.
pilotRequirement
Indicates that a certain condition, qualification, or resource is required in order for a pilot to operate or perform a specified activity.
-
D.
approximatePilots
Indicates that one entity serves as an estimated or provisional pilot for another, rather than an exact or final pilot assignment.
-
E.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a03433dd64c8190ab620709153b6278 |
completed | May 12, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_6a034107e53881909127bac98cac3429 |
completed | May 12, 2026, 3:02 p.m. |
Created at: May 1, 2026, 1:43 a.m.