Triple
T21015504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakefield Trinity |
E517662
|
entity |
| Predicate | homeGround |
P890
|
FINISHED |
| Object | Belle Vue |
—
|
NE NERFINISHED |
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: Belle Vue | Statement: [Wakefield Trinity, homeGround, Belle Vue]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belle Vue Context triple: [Wakefield Trinity, homeGround, Belle Vue]
-
A.
Belle Vue
Belle Vue was a historic football stadium in Doncaster, England, best known as the long-time home of Doncaster Rovers F.C.
-
B.
Belle Vue
Belle Vue is a small settlement on the island of Tortola in the British Virgin Islands.
-
C.
Belle Vue
Belle Vue is a district in Manchester, England, historically known for its former zoological gardens and amusement park.
-
D.
Belle Vue
chosen
Belle Vue is a historic rugby league stadium in Wakefield, West Yorkshire, best known as the long-time home of the Wakefield Trinity club.
-
E.
Belle Vue Park
Belle Vue Park is a public green space in Sudbury, England, offering recreational areas, walking paths, and community amenities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc58272881908a61eda7755ed332 |
completed | April 21, 2026, 4:26 a.m. |
Created at: April 16, 2026, 1:54 p.m.