Triple
T18211782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull Derby |
E436049
|
entity |
| Predicate | fanBaseDivision |
P130246
|
FINISHED |
| Object | divides city of Hull between two clubs |
—
|
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: divides city of Hull between two clubs | Statement: [Hull Derby, fanBaseDivision, divides city of Hull between two clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseDivision Context triple: [Hull Derby, fanBaseDivision, divides city of Hull between two clubs]
-
A.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
featuredDivision
Indicates that one division is highlighted or given special prominence in relation to others within a particular context.
-
C.
fanBaseScope
Indicates the extent or range of people who are considered fans or followers of an entity.
-
D.
gameDivision
Indicates a hierarchical or categorical separation of a game into distinct parts, sections, or groups.
-
E.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
- F. None of above. chosen
Provenance (4 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2296f8081908247a6dd08f99b25 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.