Triple
T21533859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit Courts of Virginia |
E531299
|
entity |
| Predicate | recordsMaintained |
P139163
|
FINISHED |
| Object | land records |
—
|
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: land records | Statement: [Circuit Courts of Virginia, recordsMaintained, land records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsMaintained Context triple: [Circuit Courts of Virginia, recordsMaintained, land records]
-
A.
recordKeepingSystem
Indicates a relationship where an entity functions as or is associated with a system used to store, manage, and maintain records or information.
-
B.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
-
C.
recordsWith
chosen
Indicates that one entity keeps or maintains documented information about another entity or event.
-
D.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
E.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0b9888819094e424d33c14d5d0 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.