Triple
T13605386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherwood Forest Plantation |
E325047
|
entity |
| Predicate | VirginiaLandmarkRegisterNumber |
P110382
|
FINISHED |
| Object | 018-0022 |
—
|
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: 018-0022 | Statement: [Sherwood Forest Plantation, VirginiaLandmarkRegisterNumber, 018-0022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VirginiaLandmarkRegisterNumber Context triple: [Sherwood Forest Plantation, VirginiaLandmarkRegisterNumber, 018-0022]
-
A.
VirginiaLandmarksRegisterListingDate
Indicates the date on which a place or property was officially listed in the Virginia Landmarks Register.
-
B.
locationRelativeToRichmond
Indicates the spatial or geographic position of one place in relation to the reference location Richmond.
-
C.
populationRankInVirginia
Indicates the relative position of an entity in terms of population size compared to other entities within Virginia.
-
D.
countyNumberInVirginia
Indicates that a given county is assigned a specific official county number within the state of Virginia.
-
E.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:50 p.m.