Triple
T21002414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Million Programme era |
E517326
|
entity |
| Predicate | amenityIncluded |
P79291
|
FINISHED |
| Object | central heating |
—
|
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: central heating | Statement: [Million Programme era, amenityIncluded, central heating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amenityIncluded Context triple: [Million Programme era, amenityIncluded, central heating]
-
A.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
B.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
C.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
D.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
E.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc38b8688190860fba1b58e1b3e6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.