Triple
T27224178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merton and Wandsworth |
E681363
|
entity |
| Predicate | electsMemberTo |
P109297
|
FINISHED |
| Object | London Assembly |
—
|
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 Assembly | Statement: [Merton and Wandsworth, electsMemberTo, London Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electsMemberTo Context triple: [Merton and Wandsworth, electsMemberTo, London Assembly]
-
A.
electsRole
Indicates that one entity selects or votes another entity into a specific role or position.
-
B.
elects
Indicates that one entity selects or chooses another entity for a position, role, or office, typically through a formal voting process.
-
C.
electsAt
Indicates that an election or selection of someone or something to a position, role, or office occurs at a specific time or in a specific context.
-
D.
electsForBody
chosen
Indicates that one entity chooses or votes to select another entity to serve as a member of a governing or decision-making body.
-
E.
elected to
Indicates that an entity has been chosen, typically by a vote or formal decision process, to assume a particular position, role, or office.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 9:43 a.m.