Triple
T28026838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grassy Lick, West Virginia |
E708146
|
entity |
| Predicate | servicesProvidedBy |
P59424
|
FINISHED |
| Object | Hampshire County, West 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: Hampshire County, West Virginia | Statement: [Grassy Lick, West Virginia, servicesProvidedBy, Hampshire County, West Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicesProvidedBy Context triple: [Grassy Lick, West Virginia, servicesProvidedBy, Hampshire County, West Virginia]
-
A.
servicesType
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
D.
providesServices
chosen
Indicates that one entity supplies or performs services for the benefit or use of another entity.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 8:13 p.m.