Triple
T20315171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Electric |
E510359
|
entity |
| Predicate | servedCustomersIn |
P33576
|
FINISHED |
| Object | southern England |
—
|
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: southern England | Statement: [Southern Electric, servedCustomersIn, southern England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCustomersIn Context triple: [Southern Electric, servedCustomersIn, southern England]
-
A.
servesCustomer
Indicates that one entity provides service, assistance, or products to another entity in the role of a customer.
-
B.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
C.
servedTimeFor
Indicates that one entity has completed or spent a specified duration of time serving a sentence, obligation, or term on behalf of another entity or for a particular case or offense.
-
D.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
exportCustomersCountEstimate
Indicates an estimated number of customers included in an export operation.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67786f4dc8190b02a6c2a4338362d |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.