Triple
T26251677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maldon and East Chelmsford (UK Parliament constituency) |
E656607
|
entity |
| Predicate | existsFrom |
P160410
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Maldon and East Chelmsford (UK Parliament constituency), existsFrom, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsFrom Context triple: [Maldon and East Chelmsford (UK Parliament constituency), existsFrom, 1997]
-
A.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
B.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
C.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
D.
existsBecauseOf
Indicates that one entity’s existence is caused, enabled, or brought about by another entity.
-
E.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dca3cb881908b89f0ace35212fe |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:07 p.m.