Triple
T25204208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pordenone Calcio |
E631203
|
entity |
| Predicate | regionLeagueAffiliation |
P167250
|
FINISHED |
| Object | Lega Pro |
—
|
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: Lega Pro | Statement: [Pordenone Calcio, regionLeagueAffiliation, Lega Pro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionLeagueAffiliation Context triple: [Pordenone Calcio, regionLeagueAffiliation, Lega Pro]
-
A.
regionLeague
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
B.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
-
C.
countryLeagueRepresents
Indicates that a particular league serves as the official representative or embodiment of a country in a given sport or competitive context.
-
D.
leagueAffiliationManaged
Indicates that one entity manages, oversees, or administers the league affiliation of another entity.
-
E.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 21, 2026, 12:52 p.m.