Triple
T25478172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirlingshire |
E638490
|
entity |
| Predicate | modernSuccessorArea |
P143232
|
FINISHED |
| Object | East Dunbartonshire council area |
E237306
|
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: East Dunbartonshire council area | Statement: [Stirlingshire, modernSuccessorArea, East Dunbartonshire council area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSuccessorArea Context triple: [Stirlingshire, modernSuccessorArea, East Dunbartonshire council area]
-
A.
successorArea
chosen
Indicates that one area directly follows or replaces another area in a defined sequence, progression, or versioning of areas.
-
B.
modernStateSuccessor
Indicates that one modern state is the legal, political, or historical successor to another earlier state.
-
C.
successorDivision
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
D.
successorFacility
Indicates that one facility directly follows and replaces another in function, ownership, or operation.
-
E.
successorSite
Indicates that one site directly follows and replaces another site in a sequence or evolution of sites.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10d9ea31048190ab004e697087fb06 |
completed | May 22, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:26 p.m.