Triple
T33898297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loudoun County, Colony of Virginia |
E868974
|
entity |
| Predicate | hadParishes |
P83706
|
FINISHED |
| Object | Anglican parishes |
—
|
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: Anglican parishes | Statement: [Loudoun County, Colony of Virginia, hadParishes, Anglican parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadParishes Context triple: [Loudoun County, Colony of Virginia, hadParishes, Anglican parishes]
-
A.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
-
B.
numberOfParishes
Indicates the total count of parishes associated with a given entity.
-
C.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
-
D.
parishesIncluded
chosen
Indicates that certain parishes are contained within, or form part of, a larger administrative, geographic, or organizational unit.
-
E.
hasParallelDiocese
Indicates that one diocese corresponds to and operates in parallel with another diocese, typically covering the same or overlapping territory or community under a different jurisdiction or tradition.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.