Triple
T29925489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield DocFest |
E760068
|
entity |
| Predicate | regionHost |
P79811
|
FINISHED |
| Object | Yorkshire and the Humber |
—
|
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: Yorkshire and the Humber | Statement: [Sheffield DocFest, regionHost, Yorkshire and the Humber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHost Context triple: [Sheffield DocFest, regionHost, Yorkshire and the Humber]
-
A.
mainHostRegion
Indicates the primary geographic or network region in which a host or hosting environment is located or operates.
-
B.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
-
C.
typicalHostRegion
chosen
Indicates the geographic region where a host is most commonly or characteristically found or associated.
-
D.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
E.
regionHubFor
Indicates that one region functions as a central hub or primary coordinating center for another region or set of regions.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 29, 2026, 6:16 p.m.