Triple
T25274884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLKK |
E633668
|
entity |
| Predicate | servesAsCodeFor |
P9567
|
FINISHED |
| Object | main international gateway serving Lusaka |
—
|
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: main international gateway serving Lusaka | Statement: [FLKK, servesAsCodeFor, main international gateway serving Lusaka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsCodeFor Context triple: [FLKK, servesAsCodeFor, main international gateway serving Lusaka]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
isServedByCode
Indicates that a service, resource, or item is provided, delivered, or fulfilled through a specific code.
-
C.
isOfficialCodeFor
chosen
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
D.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
E.
servesCodename
Indicates that one entity provides or uses another entity under a specific codename or alias.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 1:17 p.m.