Triple
T26878473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King County Library System |
E676820
|
entity |
| Predicate | excludesServiceArea |
P2164
|
FINISHED |
| Object | Seattle |
—
|
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: Seattle | Statement: [King County Library System, excludesServiceArea, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesServiceArea Context triple: [King County Library System, excludesServiceArea, Seattle]
-
A.
excludesRegion
chosen
Indicates that one entity explicitly omits, leaves out, or does not apply to a specified region or geographic area.
-
B.
includesAreasOff
Indicates that something encompasses or covers areas that are turned off, inactive, or excluded from normal operation.
-
C.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
-
D.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
E.
hasPrimaryServiceArea
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 5:37 a.m.