Triple
T35931777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland local government regions (1975–1996) |
E1039181
|
entity |
| Predicate | hadTwoTierStructure |
P97734
|
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: [Scotland local government regions (1975–1996), hadTwoTierStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTwoTierStructure Context triple: [Scotland local government regions (1975–1996), hadTwoTierStructure, true]
-
A.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
-
B.
hadTierSystem
chosen
Indicates that an entity implemented or used a structured tier-based system, typically organizing elements into hierarchical levels or ranks.
-
C.
hadStructure
Indicates that an entity possessed or was composed of a particular structural form, configuration, or physical arrangement.
-
D.
hasTwoPartStructure
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
E.
secondLevelStructure
Indicates a relationship where one structure functions as a secondary or subordinate level within a larger, primary structure.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.