Triple
T34506359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambia Airports Corporation Limited |
E885897
|
entity |
| Predicate | operatesAirportIn |
P115936
|
FINISHED |
| Object | Lusaka |
—
|
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: Lusaka | Statement: [Zambia Airports Corporation Limited, operatesAirportIn, Lusaka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAirportIn Context triple: [Zambia Airports Corporation Limited, operatesAirportIn, Lusaka]
-
A.
operatesAirport
Indicates that one entity manages and runs the operations of an airport.
-
B.
servesAsPrimaryAirportOperatorForCity
chosen
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
C.
operatesTerminalsIn
Indicates that an entity manages or runs the operations of one or more terminals at a given location or facility.
-
D.
servesAirportICAO
Indicates that a transportation service or facility operates routes to or from the airport identified by the given ICAO code.
-
E.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
Created at: May 1, 2026, 2:01 a.m.