Triple
T14967169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Seattle Transit Tunnel |
E373218
|
entity |
| Predicate | busPowerSupply |
P11313
|
FINISHED |
| Object | trolleybus overhead wires (historical) |
—
|
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: trolleybus overhead wires (historical) | Statement: [Downtown Seattle Transit Tunnel, busPowerSupply, trolleybus overhead wires (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busPowerSupply Context triple: [Downtown Seattle Transit Tunnel, busPowerSupply, trolleybus overhead wires (historical)]
-
A.
powering
Indicates that one entity supplies energy or power that enables another entity to operate or function.
-
B.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
C.
suppliesPowerTo
chosen
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
E.
powerAdapter
Indicates that one entity serves as a power adapter, converting or supplying electrical power for 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:47 a.m.