Triple
T15125155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburghshire |
E361266
|
entity |
| Predicate | usedAsLieutenancyAreaUntil |
P117424
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Edinburghshire, usedAsLieutenancyAreaUntil, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsLieutenancyAreaUntil Context triple: [Edinburghshire, usedAsLieutenancyAreaUntil, 1975]
-
A.
hasLieutenancyArea
Indicates that an entity falls within, is administered by, or is associated with a specific lieutenancy area (a ceremonial or administrative jurisdiction).
-
B.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
C.
historicLieutenancyArea
Indicates that an entity is located within or associated with a historic lieutenancy area (a former ceremonial or administrative jurisdiction under a lord-lieutenant).
-
D.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
E.
existedAsAdministrativeCountyFrom
Indicates that an entity functioned in the status of an administrative county starting from a specified point in time.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a0c6888190840de4ead2306544 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.