Triple
T34717191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanquhar |
E1000809
|
entity |
| Predicate | hasHistoricCountry |
P138136
|
FINISHED |
| Object | Scotland |
—
|
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: Scotland | Statement: [Sanquhar, hasHistoricCountry, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountry Context triple: [Sanquhar, hasHistoricCountry, Scotland]
-
A.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
B.
hasFormerCountry
Indicates that an entity was previously part of, or belonged to, a country that no longer exists in its former political form.
-
C.
hasHistoricalCountrySubdivision
Indicates that one entity was a territorial or administrative subdivision of a historical country.
-
D.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
E.
historicallyAssociatedWithModernCountry
chosen
Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
- 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_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.