Triple
T16914306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finland national football team |
E410282
|
entity |
| Predicate | eloHighestRankYear |
P103761
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Finland national football team, eloHighestRankYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eloHighestRankYear Context triple: [Finland national football team, eloHighestRankYear, 2002]
-
A.
eloHighestRanking
Indicates that one entity holds the highest Elo rating or ranking within a specified group or context relative to other entities.
-
B.
eloRankingBestYear
chosen
Indicates the year in which an entity achieved its highest Elo ranking.
-
C.
highestSinglesRanking
Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
-
D.
peakedWithinTopTenOn
Indicates that something (such as a work, product, or performance) reached a highest ranking position within the top ten on a specified chart, list, or ranking system.
-
E.
yearOfHighestSinglesRanking
Indicates the specific year in which an entity achieved its highest-ever singles ranking.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3f1a2c8190a512ccc09a080eb4 |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.