Triple
T34716472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annan |
E1000783
|
entity |
| Predicate | hasHistoricBurghStatus |
P195087
|
FINISHED |
| Object | royal burgh |
—
|
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: royal burgh | Statement: [Annan, hasHistoricBurghStatus, royal burgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBurghStatus Context triple: [Annan, hasHistoricBurghStatus, royal burgh]
-
A.
hasHistoricSheriffdomStatus
Indicates that an entity holds or held the official status of a historic sheriffdom within a given jurisdiction.
-
B.
hasHistoricTownRights
chosen
Indicates that an entity possesses officially granted historic town rights, typically conferring a traditional legal or municipal status as a town.
-
C.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
hasHistoricSheriffdom
Indicates that one entity was historically under the jurisdiction or authority of a particular sheriffdom.
-
E.
hasHistoricCountySeat
Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.