Triple
T27217670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esholt, West Yorkshire |
E681182
|
entity |
| Predicate | EsholtHallUsedAs |
P163481
|
FINISHED |
| Object | conference centre |
—
|
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: conference centre | Statement: [Esholt, West Yorkshire, EsholtHallUsedAs, conference centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EsholtHallUsedAs Context triple: [Esholt, West Yorkshire, EsholtHallUsedAs, conference centre]
-
A.
EsholtHallUsedAs
chosen
Indicates that Esholt Hall served a particular function or purpose during a specified period or context.
-
B.
EsholtHallInstanceOf
Indicates that Esholt Hall is an instance of, or specific example of, a particular class, type, or category.
-
C.
hasGuildhall
Indicates that an entity possesses, hosts, or is associated with a guildhall as a dedicated building or facility.
-
D.
hasHallOfResidence
Indicates that an institution or organization provides or is associated with a specific hall of residence for accommodation.
-
E.
hasGrandHall
Indicates that an entity possesses or includes a grand hall as part of its structure or facilities.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:41 a.m.