Triple
T172659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Eagle |
E3508
|
entity |
| Predicate | aircraftTypeUsed |
P1524
|
FINISHED |
| Object | regional jet |
—
|
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: regional jet | Statement: [American Eagle, aircraftTypeUsed, regional jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeUsed Context triple: [American Eagle, aircraftTypeUsed, regional jet]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
aircraftManufacturerUsed
Indicates that a particular aircraft manufacturer was employed or utilized in relation to another entity, such as for production, design, or supply purposes.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
E.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.