Triple
T27499581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Run |
E694111
|
entity |
| Predicate | isNeighborhoodInCounty |
P26304
|
FINISHED |
| Object | Fairfax County, Virginia |
—
|
NE NERFINISHED |
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: Fairfax County, Virginia | Statement: [Cherry Run, isNeighborhoodInCounty, Fairfax County, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNeighborhoodInCounty Context triple: [Cherry Run, isNeighborhoodInCounty, Fairfax County, Virginia]
-
A.
isInCountySubdivision
chosen
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
B.
isInCadastralCounty
Indicates that one entity is located within, and administratively belongs to, a specific cadastral county used for land and property registration.
-
C.
isInCountySeatAreaOfInfluence
Indicates that one location lies within the geographic or functional area of influence of a county seat.
-
D.
hasNearbyCounty
Indicates that one county is geographically close to or directly adjacent to another county.
-
E.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec1da1081908f1db9d4f63eeb85 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:10 p.m.