Triple
T1393629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Nations League |
E30615
|
entity |
| Predicate | rankingUse |
P12770
|
FINISHED |
| Object | seeding for UEFA competitions draws |
—
|
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: seeding for UEFA competitions draws | Statement: [UEFA Nations League, rankingUse, seeding for UEFA competitions draws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingUse Context triple: [UEFA Nations League, rankingUse, seeding for UEFA competitions draws]
-
A.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
B.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
C.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
D.
usesRank
chosen
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
E.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37cd99081908d16014e0b99992d |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.