Triple
T24769368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asheville metropolitan area |
E619677
|
entity |
| Predicate | associatedRegionallyWith |
P12445
|
FINISHED |
| Object | Western North Carolina |
—
|
NE NERFINISHED |
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: Western North Carolina | Statement: [Asheville metropolitan area, associatedRegionallyWith, Western North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRegionallyWith Context triple: [Asheville metropolitan area, associatedRegionallyWith, Western North Carolina]
-
A.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
B.
associatedRegionFeature
Indicates that something is linked or connected to a particular geographic or regional feature.
-
C.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
D.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
E.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 4:29 a.m.