Triple
T38058685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Footballer of the Year 2000 |
E950273
|
entity |
| Predicate | inceptionAsEdition |
P127318
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Polish Footballer of the Year 2000, inceptionAsEdition, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsEdition Context triple: [Polish Footballer of the Year 2000, inceptionAsEdition, 2000]
-
A.
inceptionOfEdition
chosen
Indicates the event or point in time at which a particular edition of a work is first created, initiated, or brought into existence.
-
B.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
C.
inceptionBefore
Indicates that one entity’s beginning, creation, or initiation occurs earlier in time than that of another entity.
-
D.
inceptionSeason
Indicates the season in which something (such as a series, competition, or activity) first began or was introduced.
-
E.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.