Triple
T36882655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling |
E911520
|
entity |
| Predicate | hasRegionalGovernmentType |
P189563
|
FINISHED |
| Object | regional council |
—
|
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: regional council | Statement: [Stirling, hasRegionalGovernmentType, regional council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalGovernmentType Context triple: [Stirling, hasRegionalGovernmentType, regional council]
-
A.
hasRegionalGovernmentAbove
Indicates that one governmental unit is hierarchically subordinate to, and governed or overseen by, a higher-level regional government.
-
B.
hasRegionalGovernor
Indicates that a region is administered or overseen by a specific governor responsible for its governance.
-
C.
hasProvinceGovernment
Indicates that a province is administered or governed by a specific provincial government authority.
-
D.
hasFormOfTerritorialOrganization
Indicates that one entity possesses or is structured according to a particular type or form of territorial organization.
-
E.
hasGovernmentTypeOfTerritory
chosen
Indicates that a specific territory is characterized by or operates under a particular form or system of government.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.