Triple
T26038553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 1998–99 |
E647619
|
entity |
| Predicate | decisiveTitleMatch |
P108960
|
FINISHED |
| Object | Manchester United 2–1 Tottenham Hotspur |
—
|
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: Manchester United 2–1 Tottenham Hotspur | Statement: [Premier League 1998–99, decisiveTitleMatch, Manchester United 2–1 Tottenham Hotspur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveTitleMatch Context triple: [Premier League 1998–99, decisiveTitleMatch, Manchester United 2–1 Tottenham Hotspur]
-
A.
titleDecidingMatch
chosen
Indicates a match whose outcome determines the winner of a title or championship.
-
B.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
C.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
-
D.
decidesTitleBy
Indicates that one entity determines or selects the official title assigned to another entity.
-
E.
decidingFactorForTitle
Indicates that something serves as the key criterion or primary reason for determining or awarding a particular title.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60620fb648190826cfb2fdefe4858 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:08 a.m.