Triple
T34878002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selkirkshire |
E1005930
|
entity |
| Predicate | formerAdministrativeFunction |
P5925
|
FINISHED |
| Object | local government county |
—
|
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: local government county | Statement: [Selkirkshire, formerAdministrativeFunction, local government county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAdministrativeFunction Context triple: [Selkirkshire, formerAdministrativeFunction, local government county]
-
A.
formerAdministeredBy
Indicates that an entity was previously administered or managed by another entity, but is no longer under that administration.
-
B.
formerFunction
chosen
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
-
D.
formerDepartment
Indicates that one entity previously served as a department or subunit of another entity but no longer holds that status.
-
E.
formerDirector
Indicates that one entity previously held the position of director of the other entity but no longer does.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
Created at: May 3, 2026, 4 p.m.