Triple
T13426929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Division (Scottish football) |
E313503
|
entity |
| Predicate | leagueHierarchyRole |
P10472
|
FINISHED |
| Object | below top division in Scotland |
—
|
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: below top division in Scotland | Statement: [First Division (Scottish football), leagueHierarchyRole, below top division in Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueHierarchyRole Context triple: [First Division (Scottish football), leagueHierarchyRole, below top division in Scotland]
-
A.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
B.
teamOwnershipRole
Indicates the specific ownership-related role or capacity an entity holds within a team (such as owner, co-owner, or managing owner).
-
C.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
D.
confederationRankingRole
Indicates the role or position an entity holds within a confederation’s ranking or hierarchical order.
-
E.
leagueType
chosen
Indicates the classification or category of a league within a broader organizational or competitive structure.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.