Triple
T26305495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackstock Knob |
E661669
|
entity |
| Predicate | rangeLocation |
P63804
|
FINISHED |
| Object | western North Carolina mountains |
—
|
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: western North Carolina mountains | Statement: [Blackstock Knob, rangeLocation, western North Carolina mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeLocation Context triple: [Blackstock Knob, rangeLocation, western North Carolina mountains]
-
A.
rangeRegion
chosen
Indicates that one entity defines or corresponds to the spatial or conceptual region over which another entity extends or is applicable.
-
B.
rangeEnvironment
Indicates that an entity operates or exists within a specified environmental range or conditions.
-
C.
rangeRole
Indicates that the specified role is associated with, or applies to, the range (target) of a property or relationship.
-
D.
segmentLocation
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
E.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee2f18481908de53cc9872e96f4 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:18 p.m.