Triple
T5291102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliteserien |
E119741
|
entity |
| Predicate | usesTiebreaker |
P6631
|
FINISHED |
| Object | goal difference |
—
|
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: goal difference | Statement: [Eliteserien, usesTiebreaker, goal difference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTiebreaker Context triple: [Eliteserien, usesTiebreaker, goal difference]
-
A.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
maintainsTieWith
Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
-
C.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
-
D.
hasTieGame
Indicates that a game or match has ended with both sides having the same score, resulting in no winner.
-
E.
tieToRankings
Indicates a relationship where something is linked or associated with a specific set of rankings or a ranking 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_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.