Triple
T28649451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walthamstow (UK Parliament constituency) |
E725149
|
entity |
| Predicate | previousExistence |
P192911
|
FINISHED |
| Object | 1885–1918 |
—
|
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: 1885–1918 | Statement: [Walthamstow (UK Parliament constituency), previousExistence, 1885–1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousExistence Context triple: [Walthamstow (UK Parliament constituency), previousExistence, 1885–1918]
-
A.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
B.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
C.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
D.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
E.
existedBeforeEvent
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
- F. None of above. chosen
Provenance (4 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 28, 2026, 4:51 a.m.