Triple
T11677936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Light |
E277539
|
entity |
| Predicate | serviceTerritoryIncludes |
P82
|
FINISHED |
| Object | downtown Seattle |
—
|
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: downtown Seattle | Statement: [Seattle City Light, serviceTerritoryIncludes, downtown Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTerritoryIncludes Context triple: [Seattle City Light, serviceTerritoryIncludes, downtown Seattle]
-
A.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
B.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
D.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
E.
areaServedType
Indicates the type or category of area that is served by an entity or service.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.