Triple
T36793131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Ridge Division |
E909107
|
entity |
| Predicate | raisedFromRegion |
P8263
|
FINISHED |
| Object | Blue Ridge Mountains region |
—
|
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: Blue Ridge Mountains region | Statement: [Blue Ridge Division, raisedFromRegion, Blue Ridge Mountains region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedFromRegion Context triple: [Blue Ridge Division, raisedFromRegion, Blue Ridge Mountains region]
-
A.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
B.
raisedIn
Indicates that an entity spent its formative or upbringing period within a particular place or environment.
-
C.
emergedInRegion
chosen
Indicates that something first appeared, originated, or came into existence within a specified geographic region.
-
D.
raisedBy
Indicates that one entity has been brought up, nurtured, or reared under the care, guidance, or authority of another entity.
-
E.
raisedAs
Indicates that one entity was brought up, nurtured, or reared in the role, identity, or condition specified by 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.