Triple
T21406380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NILEBIRD |
E528045
|
entity |
| Predicate | operatesFlightTypes |
P18239
|
FINISHED |
| Object | domestic flights |
—
|
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: domestic flights | Statement: [NILEBIRD, operatesFlightTypes, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFlightTypes Context triple: [NILEBIRD, operatesFlightTypes, domestic flights]
-
A.
hasTypeOfFlights
chosen
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
B.
aircraftOperationType
Indicates the specific manner or purpose for which an aircraft is being operated (e.g., commercial, private, military, training).
-
C.
aircraftTypesOperated
Indicates the types or models of aircraft that an entity (such as an airline or operator) uses or operates.
-
D.
operatesAircraftBrand
Indicates that an entity actively uses or runs aircraft belonging to a specified brand in its operations.
-
E.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1b08fdc81909b3ba01add5f6484 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:31 p.m.