Triple
T26251678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maldon and East Chelmsford (UK Parliament constituency) |
E656607
|
entity |
| Predicate | existsUntil |
P17487
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Maldon and East Chelmsford (UK Parliament constituency), existsUntil, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsUntil Context triple: [Maldon and East Chelmsford (UK Parliament constituency), existsUntil, 2010]
-
A.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
B.
extendsUntil
Indicates that something continues or remains in effect up to a specified point or limit in time or space.
-
C.
existedUntil
chosen
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
- 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_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_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:07 p.m.