Triple
T37416357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Ross |
E929720
|
entity |
| Predicate | capitalOrChiefPlace |
P37327
|
FINISHED |
| Object | Dingwall |
—
|
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: Dingwall | Statement: [Earl of Ross, capitalOrChiefPlace, Dingwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOrChiefPlace Context triple: [Earl of Ross, capitalOrChiefPlace, Dingwall]
-
A.
capitalLocation
chosen
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
B.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
C.
capitalLikeCity
Indicates that a capital city shares similar characteristics or status to a particular city.
-
D.
capitalAreaOf
Indicates that a specified area value represents the total land or geographic size of the capital city of a given entity.
-
E.
capitalOfType
Indicates that one entity serves as the capital city (or administrative capital) of a specified type of political or administrative unit represented by the other entity.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:16 p.m.