Triple
T8347035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothesay |
E196065
|
entity |
| Predicate | traditionalResidenceOf |
P14194
|
FINISHED |
| Object | Scottish monarchs |
—
|
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: Scottish monarchs | Statement: [Rothesay, traditionalResidenceOf, Scottish monarchs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalResidenceOf Context triple: [Rothesay, traditionalResidenceOf, Scottish monarchs]
-
A.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
regionOfHabitation
Indicates the geographic area or environment in which an entity typically lives or resides.
-
C.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
D.
traditionalRegionOfResidence
chosen
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
E.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
- 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_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. |
Created at: March 30, 2026, 5:58 p.m.