Triple
T34523473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Toffees |
E886337
|
entity |
| Predicate | associatedWithFutureHomeGround |
P113386
|
FINISHED |
| Object | Bramley-Moore Dock, Liverpool |
E256289
|
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: Bramley-Moore Dock, Liverpool | Statement: [The Toffees, associatedWithFutureHomeGround, Bramley-Moore Dock, Liverpool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFutureHomeGround Context triple: [The Toffees, associatedWithFutureHomeGround, Bramley-Moore Dock, Liverpool]
-
A.
associatedWithGround
Indicates that an entity has a defined connection or relationship with the ground, such as contact, support, or reference.
-
B.
associatedWithHistoricHome
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
-
C.
laterHomeGround
chosen
Indicates that one entity became the home ground of the other at a later time, after some previous home ground or earlier period.
-
D.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
E.
homeFieldAssociation
Indicates that one entity serves as the primary or home field, venue, or location associated with another entity.
- F. None of above.
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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
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. |
Created at: May 1, 2026, 2:02 a.m.