Triple
T34960235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Hopetoun |
E1008232
|
entity |
| Predicate | notableSeatRegion |
P154277
|
FINISHED |
| Object | West Lothian |
E29712
|
NE 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: West Lothian | Statement: [Earl of Hopetoun, notableSeatRegion, West Lothian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeatRegion Context triple: [Earl of Hopetoun, notableSeatRegion, West Lothian]
-
A.
notableSeat
Indicates that an entity holds or is associated with a seat, position, or place that is considered notable or significant in some context.
-
B.
notableSeatCounty
chosen
Indicates that a particular county is especially notable or significant as the seat (administrative center) associated with the subject.
-
C.
notableInRegion
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
D.
regionSeatLocatedIn
Indicates that the administrative seat or capital of a region is located within that region.
-
E.
notableTourRegion
Indicates that an entity is a region recognized as a significant or popular destination for tours or tourism.
- F. None of above.
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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b26bd6ec81909adc57d5fd12b109 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.