Triple
T15558622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helenio Herrera |
E370935
|
entity |
| Predicate | trophyWonWith |
P119173
|
FINISHED |
| Object | European Cup with Inter Milan |
—
|
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: European Cup with Inter Milan | Statement: [Helenio Herrera, trophyWonWith, European Cup with Inter Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyWonWith Context triple: [Helenio Herrera, trophyWonWith, European Cup with Inter Milan]
-
A.
competitionWonWith
Indicates that a competition was won using, involving, or in association with a particular participant, method, tool, or resource.
-
B.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
C.
trophyUse
Indicates that an entity uses, employs, or utilizes a trophy in some manner or context.
-
D.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
E.
namedAfterTrophy
Indicates that one entity has been given a name derived from or in honor of a particular trophy.
- F. None of above. chosen
Provenance (4 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04dda3ab88190ab383333ce69fe8f |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:09 a.m.