Triple
T6649665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby della Mole |
E150787
|
entity |
| Predicate | fanBaseJuventus |
P897
|
FINISHED |
| Object | widespread national and international support |
—
|
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: widespread national and international support | Statement: [Derby della Mole, fanBaseJuventus, widespread national and international support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseJuventus Context triple: [Derby della Mole, fanBaseJuventus, widespread national and international support]
-
A.
scoreJuventus
Indicates that an entity scores a goal for the Juventus football team in a match.
-
B.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
C.
JuventusFCUsePeriod
Indicates the time period during which Juventus FC is active, relevant, or under consideration in a given context.
-
D.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
E.
juventusCoach
Indicates that one entity serves as the head coach/manager of the Juventus football club.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.