Triple
T38429491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoovers |
E903758
|
entity |
| Predicate | initiallyAllocatedTo |
P108451
|
FINISHED |
| Object | London Midland Region |
—
|
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: London Midland Region | Statement: [Hoovers, initiallyAllocatedTo, London Midland Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyAllocatedTo Context triple: [Hoovers, initiallyAllocatedTo, London Midland Region]
-
A.
allottedTo
chosen
Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
-
B.
allottedBy
Indicates that something has been assigned, distributed, or allocated by a particular agent or authority.
-
C.
originallyAwardedTo
Indicates that something (such as a prize, title, or resource) was first granted or assigned to a particular recipient before any later changes or transfers.
-
D.
traditionallyAssignedTo
Indicates that something is customarily or historically designated as the responsibility, role, or domain of a particular entity according to tradition.
-
E.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:31 p.m.