Triple
T5291358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway national football team |
E119747
|
entity |
| Predicate | eloHighestRankingDate |
P50941
|
FINISHED |
| Object | October 1993 |
—
|
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: October 1993 | Statement: [Norway national football team, eloHighestRankingDate, October 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eloHighestRankingDate Context triple: [Norway national football team, eloHighestRankingDate, October 1993]
-
A.
dateOfHighestSinglesRanking
Indicates the specific date on which an entity achieved its highest-ever singles ranking.
-
B.
highestSinglesRanking
Indicates the relationship where a specific singles ranking represents the best (numerically highest) singles position an entity has ever achieved.
-
C.
fifaRankingHighestDate
Indicates the date on which an entity achieved its highest-ever FIFA ranking.
-
D.
peakRatingDate
chosen
Indicates the date on which an entity reached its highest (peak) rating within a given rating history or period.
-
E.
fifaRankingHighest
Indicates that the subject has the highest FIFA ranking among a specified group or within a given 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.