Triple
T980547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gas Works Park |
E21156
|
entity |
| Predicate | occupiesArea |
P2574
|
FINISHED |
| Object | former Seattle Gas Light Company gasification plant site |
—
|
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: former Seattle Gas Light Company gasification plant site | Statement: [Gas Works Park, occupiesArea, former Seattle Gas Light Company gasification plant site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupiesArea Context triple: [Gas Works Park, occupiesArea, former Seattle Gas Light Company gasification plant site]
-
A.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
B.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
C.
occupies
chosen
Indicates that one entity takes up or resides within a physical or conceptual space belonging to or associated with another entity.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47b58ec81908d95f151b9af3dae |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.