Triple
T35313550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitas |
E1019841
|
entity |
| Predicate | clubLeagueSystem |
P178353
|
FINISHED |
| Object | Netherlands football league system |
—
|
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: Netherlands football league system | Statement: [Vitas, clubLeagueSystem, Netherlands football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubLeagueSystem Context triple: [Vitas, clubLeagueSystem, Netherlands football league system]
-
A.
leagueSystemOfClub
chosen
Indicates the league system or competition structure in which a given club participates or is organized.
-
B.
homeClubLeagueSystem
Indicates that a club’s primary or home competition participation is within a specified league system.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
managedLeague
Indicates that one entity was responsible for organizing, directing, or overseeing the operations of a particular league.
-
E.
countryLeagueScope
Indicates that a league’s scope or coverage is defined at the level of a specific country.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.