Triple
T11442928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merton |
E271188
|
entity |
| Predicate | hasLondonBoroughStatusSince |
P35022
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Merton, hasLondonBoroughStatusSince, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLondonBoroughStatusSince Context triple: [Merton, hasLondonBoroughStatusSince, 1965]
-
A.
hasLondonBorough
Indicates that an entity includes, contains, or is associated with a specific London borough as one of its administrative subdivisions.
-
B.
createdAsLondonBorough
chosen
Indicates that an entity was formally established or designated with the status of a London borough.
-
C.
hasMetropolitanBoroughStatus
Indicates that an administrative area holds the legal and governmental status of a metropolitan borough.
-
D.
parliamentaryBoroughCreatedBefore
Indicates that one parliamentary borough was established at an earlier time than another parliamentary borough.
-
E.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d808891b7481908bf5a80cb7644061 |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.