Triple
T23203200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsliðið |
E580373
|
entity |
| Predicate | notableUpsetYear |
P151335
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Landsliðið, notableUpsetYear, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUpsetYear Context triple: [Landsliðið, notableUpsetYear, 1990]
-
A.
hasNotableUpsets
Indicates that one entity has achieved surprising or unexpected victories over another entity or entities.
-
B.
notableSelectionYear
Indicates the year in which an entity was notably selected for a particular role, honor, list, or recognition.
-
C.
notableElectionYear
Indicates that a particular year is recognized as significant or noteworthy in the context of an election involving the given entity.
-
D.
notableAccidentYear
Indicates the year in which a notable accident involving the subject occurred.
-
E.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
- F. None of above. chosen
Provenance (4 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907a8bb48190846802a24d33bccf |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:07 p.m.