Triple
T8213208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Array |
E191870
|
entity |
| Predicate | estimatedHomesPowered |
P36029
|
FINISHED |
| Object | around 500,000 homes |
—
|
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: around 500,000 homes | Statement: [London Array, estimatedHomesPowered, around 500,000 homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedHomesPowered Context triple: [London Array, estimatedHomesPowered, around 500,000 homes]
-
A.
averageHouseholdsPoweredPerYear
chosen
Indicates the typical number of households that can be supplied with power over the course of one year.
-
B.
numberOfPowerhouses
Indicates the quantity of powerhouse entities associated with or contained by a given subject.
-
C.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
D.
hasPowerHouse
Indicates that one entity possesses or contains a primary energy-producing or central operational unit (a "power house") associated with it.
-
E.
numberOfHouses
Indicates the quantity of houses associated with a given entity or context.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76e1ffa081908883338e7d3a7c6d |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.