Triple
T30698285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrico County, Virginia Colony |
E781536
|
entity |
| Predicate | originalShireOf |
P83441
|
FINISHED |
| Object | Virginia Colony |
—
|
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 Colony | Statement: [Henrico County, Virginia Colony, originalShireOf, Virginia Colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalShireOf Context triple: [Henrico County, Virginia Colony, originalShireOf, Virginia Colony]
-
A.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
-
B.
houseOfOrigin
Indicates the original location, institution, or context from which an entity first came or was initially produced.
-
C.
originalTerritory
chosen
Indicates that a specified area or region is the initial or historically established domain associated with an entity before any changes, transfers, or expansions.
-
D.
acquisitionOfShireCompletedIn
Indicates that the acquisition of the Shire entity was fully completed in the specified time or date.
-
E.
originalHomeland
Indicates the place or region that is considered the ancestral or earliest homeland of an 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: April 29, 2026, 8:34 p.m.