Triple
T19030427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince William County, Colony of Virginia |
E465719
|
entity |
| Predicate | statusAfter1776 |
P133627
|
FINISHED |
| Object | county of the Commonwealth of 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: county of the Commonwealth of Virginia | Statement: [Prince William County, Colony of Virginia, statusAfter1776, county of the Commonwealth of Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1776 Context triple: [Prince William County, Colony of Virginia, statusAfter1776, county of the Commonwealth of Virginia]
-
A.
statusAfter1970
Indicates the status or condition of an entity as it exists after the year 1970.
-
B.
statusAfter1865
Indicates the condition or state of an entity as it existed after the year 1865.
-
C.
statusAfter1799
Indicates the condition or state of something as it existed after the year 1799.
-
D.
statusAfter1996
Indicates the status or condition of an entity as it exists after the year 1996.
-
E.
statusAfter1917
Indicates the condition or state of an entity as it existed after the year 1917, typically in contrast to its prior status.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7404d748190bcb51692fb822fd4 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.