Triple
T22438640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leesylvania, Prince William County, Virginia |
E554694
|
entity |
| Predicate | primaryStructureStatus |
P126351
|
FINISHED |
| Object | ruins |
—
|
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: ruins | Statement: [Leesylvania, Prince William County, Virginia, primaryStructureStatus, ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStructureStatus Context triple: [Leesylvania, Prince William County, Virginia, primaryStructureStatus, ruins]
-
A.
primaryStructure
Indicates that one entity serves as the main or principal structural component or framework in relation to another entity.
-
B.
originalStructureStatus
chosen
Indicates the condition or state of an entity’s initial or pre-modified structure relative to its later or current form.
-
C.
primaryStatus
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
-
D.
originalStructureType
Indicates the type or category of the structure that an entity originally had before any changes or transformations.
-
E.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.