Triple
T1390912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lothian |
E29953
|
entity |
| Predicate | hasCouncilAreaStatus |
P28237
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East Lothian, hasCouncilAreaStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilAreaStatus Context triple: [East Lothian, hasCouncilAreaStatus, true]
-
A.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
B.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
C.
includesUnionTerritory
Indicates that an administrative or political entity contains one or more union territories within its jurisdiction or composition.
-
D.
hasCapitalDistrictStatus
Indicates that an administrative region holds the official status of being a capital district within a country or larger jurisdiction.
-
E.
unionTerritoryWith
Indicates that one entity is a union territory that is administratively associated or linked with another entity.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35f7ab081909fe81dd475d6196f |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.