Triple
T8347024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothesay |
E196065
|
entity |
| Predicate | wasRoyalBurgh |
P82213
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rothesay, wasRoyalBurgh, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRoyalBurgh Context triple: [Rothesay, wasRoyalBurgh, true]
-
A.
grantedRoyalBurghStatusBy
Indicates that a place or settlement has been formally conferred royal burgh status by a specific authority or ruler.
-
B.
grantedRoyalBurghStatusIn
Indicates that an authority formally conferred royal burgh status upon an entity in a specified year or at a specific time.
-
C.
wasRoyalMiningTownOf
Indicates that a town historically held official royal status and functioned as a designated center for mining activities under royal authority.
-
D.
wasRoyalManor
Indicates that a place or estate functioned as a manor owned or directly controlled by a monarch or royal authority.
-
E.
boroughOf
Indicates that one place is a borough that is administratively or geographically part of another, typically larger, municipal entity.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8013d81c81908da48466cffb3939 |
completed | March 31, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:58 p.m.