Triple
T6899140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League D |
E159448
|
entity |
| Predicate | teamRanking |
P41792
|
FINISHED |
| Object | lowest-ranked UEFA national teams |
—
|
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: lowest-ranked UEFA national teams | Statement: [League D, teamRanking, lowest-ranked UEFA national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRanking Context triple: [League D, teamRanking, lowest-ranked UEFA national teams]
-
A.
globalRanking
Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
-
B.
leagueStandingDescribed
chosen
Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
-
C.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
D.
teamScoring
Indicates that a team achieves a score or points in a game, match, or competitive event.
-
E.
SSRank
Indicates a ranking relationship that orders entities based on their social status, standing, or relative importance within a specified context.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95d67448190857f36b8115b03f6 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.