Triple
T22083518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidstone and The Weald |
E545710
|
entity |
| Predicate | AnnWiddecombeServedFrom |
P146901
|
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: [Maidstone and The Weald, AnnWiddecombeServedFrom, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AnnWiddecombeServedFrom Context triple: [Maidstone and The Weald, AnnWiddecombeServedFrom, 1997]
-
A.
servedForSide
Indicates that something is provided or presented as an accompaniment or side item to a main dish or primary element.
-
B.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
C.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
-
D.
crewServed
Indicates that the operation or use of something requires a coordinated effort by multiple people acting together as a crew.
-
E.
servedByAtNight
Indicates that a service or location is operated, attended to, or provided specifically during nighttime hours.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b803f081909a0a121aecf526ae |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:28 p.m.