Triple
T25126627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatian First Football League titles |
E629410
|
entity |
| Predicate | titleDeciderTieBreak |
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: [Croatian First Football League titles, titleDeciderTieBreak, goal difference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleDeciderTieBreak Context triple: [Croatian First Football League titles, titleDeciderTieBreak, goal difference]
-
A.
titleDecidingMatch
Indicates a match whose outcome determines the winner of a title or championship.
-
B.
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.
-
C.
titleDecidedOn
Indicates that a final decision has been made regarding the title assigned to an entity or work.
-
D.
titleDeciderFor
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
E.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:28 a.m.