Triple
T24842041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binter Canarias |
E621639
|
entity |
| Predicate | mainAircraftFamily |
P7145
|
FINISHED |
| Object | ATR 72 |
—
|
NE NERFINISHED |
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: ATR 72 | Statement: [Binter Canarias, mainAircraftFamily, ATR 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAircraftFamily Context triple: [Binter Canarias, mainAircraftFamily, ATR 72]
-
A.
commonAircraftFamily
Indicates that two aircraft belong to the same aircraft family or series, sharing a common design lineage.
-
B.
aircraftFamilyIncludes
Indicates that a particular aircraft family encompasses or contains a given aircraft model or variant as a member of that family.
-
C.
notableAircraftFamily
Indicates that one entity is a well-known or historically significant family or series of aircraft associated with the other entity.
-
D.
currentAircraftFamily
chosen
Indicates the specific family or series of aircraft that an entity is currently associated with or operating.
-
E.
airlineFleetCategory
Indicates the classification category of an airline based on the characteristics or size of its aircraft fleet.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:19 a.m.