Triple
T25459432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairobi–Entebbe |
E638001
|
entity |
| Predicate | hasDirectFlights |
P105188
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nairobi–Entebbe, hasDirectFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectFlights Context triple: [Nairobi–Entebbe, hasDirectFlights, yes]
-
A.
allInternationalFlightsRouteVia
Indicates that every international flight to or from a given location must pass through a specified intermediate location or hub.
-
B.
hasAirTravelLink
chosen
Indicates that there is a direct or established air travel connection (such as flights or air routes) between the related entities.
-
C.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
D.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
E.
airlineServiceVia
Indicates that an airline service operates between two locations with a specified intermediate stop or transit point.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 2:11 p.m.