Triple
T25276545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zambia national football team |
E633709
|
entity |
| Predicate | usesForInternationalCode |
P159738
|
FINISHED |
| Object | ZAM |
—
|
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: ZAM | Statement: [Zambia national football team, usesForInternationalCode, ZAM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForInternationalCode Context triple: [Zambia national football team, usesForInternationalCode, ZAM]
-
A.
internationalUsage
Indicates that something is used or applied across multiple countries or in an international context.
-
B.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
usedForCountry
Indicates that something is used for, or serves a purpose related to, a specific country.
-
E.
usedInInternationalBankingCode
Indicates that something is employed as part of an internationally recognized banking identification or transaction code.
- F. None of above. chosen
Provenance (4 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_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 1:17 p.m.