Triple
T10856840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bramley-Moore Dock Stadium |
E256288
|
entity |
| Predicate | clubMove |
P96093
|
FINISHED |
| Object | Everton F.C. relocation from Goodison Park |
—
|
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: Everton F.C. relocation from Goodison Park | Statement: [Bramley-Moore Dock Stadium, clubMove, Everton F.C. relocation from Goodison Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubMove Context triple: [Bramley-Moore Dock Stadium, clubMove, Everton F.C. relocation from Goodison Park]
-
A.
commonMove
Indicates that two or more entities share the same movement or relocation event, occurring together or in an identical manner.
-
B.
clubMoveYear
Indicates the year in which an entity changes or transfers its affiliation to a different club.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
movedToClub
Indicates that an entity has transferred or changed affiliation from one club to another club.
-
E.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7513695ac8190b5812e977a422c37 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.