Triple
T2603201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merseyside derby |
E58592
|
entity |
| Predicate | involvesFanbases |
P897
|
FINISHED |
| Object | Liverpool supporters |
—
|
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: Liverpool supporters | Statement: [Merseyside derby, involvesFanbases, Liverpool supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesFanbases Context triple: [Merseyside derby, involvesFanbases, Liverpool supporters]
-
A.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
C.
fanBaseScope
Indicates the extent or range of people who are considered fans or followers of an entity.
-
D.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
E.
hasFanBaseTension
Indicates a relationship where there is conflict, rivalry, or strained relations between the fan bases of the related entities.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd48241c48190bc80418212e33bc8 |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.