Triple
T2554012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinnah International Airport |
E56690
|
entity |
| Predicate | hasTaxiServices |
P24209
|
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: [Jinnah International Airport, hasTaxiServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxiServices Context triple: [Jinnah International Airport, hasTaxiServices, yes]
-
A.
hasTaxiStand
chosen
Indicates that a location or facility includes or is served by a designated taxi stand area where taxis can wait for passengers.
-
B.
coordinatesTransportationServicesWith
Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
-
C.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
D.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.