Triple
T25363260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-VA-083 |
E636028
|
entity |
| Predicate | hasJurisdictionName |
P158238
|
FINISHED |
| Object | Halifax County |
—
|
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: Halifax County | Statement: [US-VA-083, hasJurisdictionName, Halifax County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJurisdictionName Context triple: [US-VA-083, hasJurisdictionName, Halifax County]
-
A.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
B.
hasJurisidiction
Indicates that one entity holds legal authority or control over another entity, area, or matter.
-
C.
hasJurisdictionStatus
Indicates that an authority or entity holds a particular legal or administrative jurisdictional status over a specified domain, area, or matter.
-
D.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
-
E.
hasJurisdictionCharacteristic
Indicates that a jurisdiction possesses a particular legal, regulatory, or administrative characteristic.
- F. None of above. chosen
Provenance (4 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_69f4a10c2bec8190826d4e36288068a4 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:36 p.m.