Triple
T11910195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S7 stock (DLR type) |
E283372
|
entity |
| Predicate | powerSupplyCompatibility |
P44389
|
FINISHED |
| Object | Docklands Light Railway power system |
—
|
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: Docklands Light Railway power system | Statement: [S7 stock (DLR type), powerSupplyCompatibility, Docklands Light Railway power system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSupplyCompatibility Context triple: [S7 stock (DLR type), powerSupplyCompatibility, Docklands Light Railway power system]
-
A.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
B.
hasPowerSupplyType
chosen
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
C.
powerSupplyLocation
Indicates the physical place or component where an entity’s electrical power is provided or connected.
-
D.
powerAdapter
Indicates that one entity serves as a power adapter, converting or supplying electrical power for another entity.
-
E.
powerAdapterWattage
Indicates the electrical power capacity, in watts, that a power adapter can supply.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.