Triple
T521046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Fairfax |
E10816
|
entity |
| Predicate | isLocalGovernmentCenterFor |
P11028
|
FINISHED |
| Object | Fairfax County area |
—
|
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: Fairfax County area | Statement: [City of Fairfax, isLocalGovernmentCenterFor, Fairfax County area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalGovernmentCenterFor Context triple: [City of Fairfax, isLocalGovernmentCenterFor, Fairfax County area]
-
A.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
B.
isMajorCenterOf
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
C.
governmentCenter
chosen
Indicates that a location serves as the primary administrative or political hub for a government or governing body.
-
D.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
E.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1a1817c8190a6cc8f423071d3ad |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f016ba5c81909825b04e7525b4ab |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.