Triple
T22083840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunbridge Wells Hospital at Pembury |
E545719
|
entity |
| Predicate | constructionCompletion |
P1511
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Tunbridge Wells Hospital at Pembury, constructionCompletion, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionCompletion Context triple: [Tunbridge Wells Hospital at Pembury, constructionCompletion, 2011]
-
A.
constructionCompleted
chosen
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
C.
constructionPhase
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
D.
constructionResumed
Indicates that previously halted construction activity on an entity or project has started again.
-
E.
constructionExpanded
Indicates that a construction project or structure has been enlarged or extended beyond its original size or scope.
- 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_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. |
Created at: April 16, 2026, 8:28 p.m.