Triple
T23874659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Atholl |
E592830
|
entity |
| Predicate | notableSeatCounty |
P154277
|
FINISHED |
| Object | Perth and Kinross |
—
|
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: Perth and Kinross | Statement: [Marquess of Atholl, notableSeatCounty, Perth and Kinross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeatCounty Context triple: [Marquess of Atholl, notableSeatCounty, Perth and Kinross]
-
A.
notableCounty
Indicates that a county holds particular significance or prominence in relation to the subject.
-
B.
hasCountySeatCounty
Indicates that a county seat is administratively associated with and serves as the seat of government for a specific county.
-
C.
traditionalSeatCounty
Indicates that a location serves as the historically recognized administrative or ceremonial county seat for a given county.
-
D.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
E.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc00420c8190b841ea15044961d8 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:15 p.m.