Triple
T24153455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King and Queen County, Virginia |
E598604
|
entity |
| Predicate | isHistoricRegion |
P141237
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [King and Queen County, Virginia, isHistoricRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricRegion Context triple: [King and Queen County, Virginia, isHistoricRegion, true]
-
A.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
B.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
C.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
D.
hasHistoricRegionStyle
Indicates that an entity exhibits or is characterized by the architectural or cultural style associated with a particular historic region.
-
E.
isHistoricallyDistinctRegion
chosen
Indicates that a region is recognized as a separate and distinct territorial or cultural entity in historical context, differing from surrounding or successor regions.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e2e83081908e543ef266a27ec9 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.