Triple
T25362976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Virgilina, Virginia |
E636020
|
entity |
| Predicate | borderSettlementBetween |
P46520
|
FINISHED |
| Object | Virginia |
—
|
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: Virginia | Statement: [Town of Virgilina, Virginia, borderSettlementBetween, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSettlementBetween Context triple: [Town of Virgilina, Virginia, borderSettlementBetween, Virginia]
-
A.
borderSettlement
chosen
Indicates that a settlement is located near or along a political or administrative border.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
D.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
E.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 1:36 p.m.