Triple
T25427507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blenheim Walk campus |
E637153
|
entity |
| Predicate | isKeySiteOf |
P161457
|
FINISHED |
| Object | Leeds Arts University |
—
|
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: Leeds Arts University | Statement: [Blenheim Walk campus, isKeySiteOf, Leeds Arts University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySiteOf Context triple: [Blenheim Walk campus, isKeySiteOf, Leeds Arts University]
-
A.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
isSatelliteSiteOf
Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
-
C.
hasKeyArchaeologicalSite
Indicates that an entity is associated with or possesses a primary or significant archaeological site.
-
D.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
E.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 21, 2026, 1:57 p.m.