Triple
T4640650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull Kingston Rovers |
E101645
|
entity |
| Predicate | playsInTier |
P23582
|
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: [Hull Kingston Rovers, playsInTier, top tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInTier Context triple: [Hull Kingston Rovers, playsInTier, top tier]
-
A.
playsInTopTier
chosen
Indicates that an entity participates as a competitor in the highest-level division or league within a given sport or competitive system.
-
B.
tierInLeagueSystem
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
C.
athleticAssociationTier
Indicates the competitive level or division within an athletic association to which an entity (such as a team or institution) belongs.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
tierInNationalFootball
Indicates the competitive level or division within a country's national football league system in which an entity (e.g., a club or team) participates.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8fbd2c8190b593cd46ce8dfe0f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.