Triple
T25627995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison County, Virginia |
E642487
|
entity |
| Predicate | onFrontierOf |
P128245
|
FINISHED |
| Object | western Virginia |
—
|
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 Virginia | Statement: [Harrison County, Virginia, onFrontierOf, western Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onFrontierOf Context triple: [Harrison County, Virginia, onFrontierOf, western Virginia]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
C.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
D.
frontsOn
chosen
Indicates that one entity directly faces, borders, or has its primary side along the edge of another entity, such as a building fronting on a street or a property fronting on a body of water.
-
E.
frontierImplication
Indicates that one condition or state at a boundary or limit logically leads to, constrains, or entails another condition or state at that boundary.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa25423081908a40d12f99afebad |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:16 p.m.