Triple
T35929763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL |
E1039125
|
entity |
| Predicate | usedAsFIFACountryCode |
P185147
|
FINISHED |
| Object | POL |
—
|
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: POL | Statement: [PL, usedAsFIFACountryCode, POL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFIFACountryCode Context triple: [PL, usedAsFIFACountryCode, POL]
-
A.
correspondingFIFACode
Indicates that one entity is associated with, or mapped to, its corresponding official FIFA code.
-
B.
FIPSCountryCode
Indicates that an entity is associated with a specific country as identified by its FIPS (Federal Information Processing Standards) country code.
-
C.
fifaCodeUsedBy
chosen
Indicates that a specific FIFA country or team code is used to represent or identify a particular team, association, or entity in the context of FIFA competitions or records.
-
D.
homeCountryFIFA_code
Indicates the FIFA country code that represents the national association or home country with which an entity is affiliated.
-
E.
usedForSportsCountryCodes
Indicates that the referenced country codes are those used specifically for identifying countries in sports contexts or competitions.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:07 p.m.