Triple
T32461891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coppa Italia Serie C |
E829595
|
entity |
| Predicate | involvesClubLevel |
P79957
|
FINISHED |
| Object | Serie C |
—
|
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: Serie C | Statement: [Coppa Italia Serie C, involvesClubLevel, Serie C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesClubLevel Context triple: [Coppa Italia Serie C, involvesClubLevel, Serie C]
-
A.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
B.
includesClubLevel
chosen
Indicates that one entity encompasses or provides access to a specific club-level tier, area, or privileges associated with another entity.
-
C.
clubTypeInvolved
Indicates that a specific type or category of club is involved or participates in the referenced event, activity, or relationship.
-
D.
alsoInvolvesClubsFrom
Indicates that an event, action, or relationship includes participation or involvement of clubs originating from a specified place or region.
-
E.
supportsClubLeagueLevel
Indicates that an entity provides backing or resources enabling a club to participate at a specific league level.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 12:57 a.m.