Triple
T11763466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staffordshire County Council |
E279712
|
entity |
| Predicate | higherTierOf |
P7937
|
FINISHED |
| Object | district councils in Staffordshire |
—
|
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: district councils in Staffordshire | Statement: [Staffordshire County Council, higherTierOf, district councils in Staffordshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherTierOf Context triple: [Staffordshire County Council, higherTierOf, district councils in Staffordshire]
-
A.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
B.
higherTierAuthority
chosen
Indicates that one entity holds a superior or higher-ranking level of authority or control over another entity.
-
C.
upperTierHeight
Indicates the vertical measurement or elevation of an upper tier relative to a reference level or structure.
-
D.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
E.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5248e0881909ed1b4df7be422f7 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.