Triple
T19682097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finlarig Castle |
E472617
|
entity |
| Predicate | referenceInRegister |
P28085
|
FINISHED |
| Object | Canmore ID 23974 |
—
|
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: Canmore ID 23974 | Statement: [Finlarig Castle, referenceInRegister, Canmore ID 23974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceInRegister Context triple: [Finlarig Castle, referenceInRegister, Canmore ID 23974]
-
A.
symbolReferenced
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
B.
relatedRegister
chosen
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
C.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
D.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
E.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c05964819093d3124b8f174001 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.