Triple
T38058159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A 2005–06 with Inter Milan |
E950261
|
entity |
| Predicate | titleAwardContext |
P16522
|
FINISHED |
| Object | Calciopoli scandal |
—
|
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: Calciopoli scandal | Statement: [Serie A 2005–06 with Inter Milan, titleAwardContext, Calciopoli scandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAwardContext Context triple: [Serie A 2005–06 with Inter Milan, titleAwardContext, Calciopoli scandal]
-
A.
awardContext
chosen
Indicates the situational or circumstantial context in which an award is given or received.
-
B.
awardsTitle
Indicates that an entity confers or grants a specific title or honorific designation to another entity.
-
C.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
-
D.
awardName
Indicates the specific name or title of an award associated with an entity.
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 3, 2026, 4:21 p.m.