Triple
T34523451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Toffees |
E886337
|
entity |
| Predicate | associatedWithCityRival |
P205454
|
FINISHED |
| Object | Liverpool F.C. |
E8494
|
NE 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: Liverpool F.C. | Statement: [The Toffees, associatedWithCityRival, Liverpool F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCityRival Context triple: [The Toffees, associatedWithCityRival, Liverpool F.C.]
-
A.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
B.
rivalryInvolvesCity
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
C.
rivalClubsInSameCity
Indicates that two sports clubs are rivals and are based in the same city.
-
D.
isPartOfRivalry
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
-
E.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
- F. None of above. chosen
Provenance (5 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729e50d0481908217a2f6ff9fd443 |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:02 a.m.