Triple
T26489422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFFHS Player of the Century awards |
E669114
|
entity |
| Predicate | geographicalBreakdown |
P84967
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [IFFHS Player of the Century awards, geographicalBreakdown, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalBreakdown Context triple: [IFFHS Player of the Century awards, geographicalBreakdown, worldwide]
-
A.
geographicalUsage
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
B.
geographicDivision
Indicates that one place is an administrative or territorial subdivision of another place.
-
C.
distributionByCountry
chosen
Indicates how something is allocated, spread, or categorized according to different countries.
-
D.
geographicalStructure
Indicates a relationship where one entity is a physical geographic feature or formation that characterizes or shapes the spatial nature of another entity or area.
-
E.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 1:02 a.m.