Triple
T18583922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viareggini |
E454189
|
entity |
| Predicate | associatedWithLocalSport |
P78147
|
FINISHED |
| Object | Viareggio football clubs |
—
|
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: Viareggio football clubs | Statement: [Viareggini, associatedWithLocalSport, Viareggio football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLocalSport Context triple: [Viareggini, associatedWithLocalSport, Viareggio football clubs]
-
A.
associatedWithCitySports
Indicates a relationship where an entity has a connection or involvement with city-level sports activities, organizations, or events.
-
B.
hasLocalSport
chosen
Indicates that a place or community is associated with, supports, or regularly engages in a particular sport at the local level.
-
C.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
D.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
E.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543d200dc8190b8797d731f4e4865 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.