Triple
T33007114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberdrola |
E844532
|
entity |
| Predicate | keySubsidiary |
P175904
|
FINISHED |
| Object | ScottishPower |
—
|
NE NERFINISHED |
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: ScottishPower | Statement: [Iberdrola, keySubsidiary, ScottishPower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySubsidiary Context triple: [Iberdrola, keySubsidiary, ScottishPower]
-
A.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
-
B.
keyOffice
Indicates that a key is associated with, grants access to, or is assigned to a particular office.
-
C.
keyAccord
Indicates that one entity’s key or signature matches, agrees with, or is compatible with that of another entity.
-
D.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
-
E.
keyBase
Indicates that one entity serves as the primary or foundational key upon which another entity or structure is based.
- F. None of above. chosen
Provenance (4 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:23 a.m.