Triple
T28138779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Electricity Authority |
E714283
|
entity |
| Predicate | natureOfOwnership |
P7585
|
FINISHED |
| Object | state-owned |
—
|
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: state-owned | Statement: [British Electricity Authority, natureOfOwnership, state-owned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfOwnership Context triple: [British Electricity Authority, natureOfOwnership, state-owned]
-
A.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
ownershipStructure
Indicates how ownership or control is distributed among entities within an organization or asset.
-
C.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
-
D.
ownershipCharacteristic
Indicates that one entity possesses a particular quality, attribute, or condition specifically in its role as an owner of another entity.
-
E.
ownershipDifferenceFrom
Indicates a relationship where the ownership status or set of owners of one entity differs from that of 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:51 p.m.