Triple
T16285945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Core Based Statistical Area |
E395387
|
entity |
| Predicate | hasHigherLevelGrouping |
P33477
|
FINISHED |
| Object | Combined Statistical Area |
—
|
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: Combined Statistical Area | Statement: [Core Based Statistical Area, hasHigherLevelGrouping, Combined Statistical Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherLevelGrouping Context triple: [Core Based Statistical Area, hasHigherLevelGrouping, Combined Statistical Area]
-
A.
hasPriorityGroup
Indicates that one entity is assigned to, or associated with, a specific priority group relative to others.
-
B.
hasMultipleLevels
Indicates that something is organized into more than one hierarchical or structural level.
-
C.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
D.
hasCategoryLevel
chosen
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
-
E.
containsGroup
Indicates that one entity includes or encompasses a specific group of entities within it.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.