Triple
T17501115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie County Holding Center |
E426187
|
entity |
| Predicate | facilityLevel |
P98032
|
FINISHED |
| Object | local |
—
|
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: local | Statement: [Erie County Holding Center, facilityLevel, local]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facilityLevel Context triple: [Erie County Holding Center, facilityLevel, local]
-
A.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
-
B.
hasFacilityLevel
chosen
Indicates the degree or tier of capability, service, or infrastructure that a particular facility possesses.
-
C.
facilityScope
Indicates the extent or boundaries of responsibility, service, or operation associated with a particular facility.
-
D.
facilityId
Indicates a relationship that associates an entity with the unique identifier of the facility it belongs to or is located in.
-
E.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45212140c8190a2987ffabbacce22 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.