Triple
T35929762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL |
E1039125
|
entity |
| Predicate | usedAsOlympicCountryCode |
P121164
|
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, usedAsOlympicCountryCode, POL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOlympicCountryCode Context triple: [PL, usedAsOlympicCountryCode, POL]
-
A.
homeCountryIOCCode
Indicates the International Olympic Committee (IOC) country code that represents an entity’s home or primary national affiliation.
-
B.
usedForSportsCountryCodes
chosen
Indicates that the referenced country codes are those used specifically for identifying countries in sports contexts or competitions.
-
C.
hasOlympicCountry
Indicates that an entity is associated with or represents a specific country in the context of the Olympic Games.
-
D.
OlympicStatus
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
-
E.
recognizedByInternationalOlympicCommittee
Indicates that something has been officially acknowledged or accepted by the International Olympic Committee as meeting its standards or status criteria.
- 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_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:07 p.m.