Triple
T10419605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness Cathedral |
E245610
|
entity |
| Predicate | isRiversideBuilding |
P25973
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Inverness Cathedral, isRiversideBuilding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRiversideBuilding Context triple: [Inverness Cathedral, isRiversideBuilding, yes]
-
A.
isRiverside
Indicates that one entity is located beside or along the bank of a river in relation to another entity.
-
B.
isRiversideRangeOf
Indicates that something is a range or stretch of land that lies along the side of a river.
-
C.
isWaterfrontBuilding
chosen
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
-
E.
isRiversideExpansionOf
Indicates that one riverside area is an extension, enlargement, or developed continuation of another along the same river.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2aa7848190a7091ee71722fcc6 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:11 p.m.