Triple
T3317724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Dukla Trenčín |
E69719
|
entity |
| Predicate | homeCountryLeagueTier |
P27783
|
FINISHED |
| Object | top tier |
—
|
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: top tier | Statement: [HC Dukla Trenčín, homeCountryLeagueTier, top tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryLeagueTier Context triple: [HC Dukla Trenčín, homeCountryLeagueTier, top tier]
-
A.
homeCountryLeagueLevel
chosen
Indicates the competitive tier or division level of the league in the subject’s home country with which the subject is associated.
-
B.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
-
C.
countryOfLeague
Indicates the country in which a given league is based or officially belongs.
-
D.
homeCountryFIFA_code
Indicates the FIFA country code that represents the national association or home country with which an entity is affiliated.
-
E.
homeCountryLeaguePyramid
Indicates the league system or hierarchy of competitions that serves as the domestic football/sports pyramid in the entity’s home 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb113cb6c8190989b06476f6015fd |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.