Triple
T8976719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumbernauld |
E214408
|
entity |
| Predicate | townCentreOpening |
P86028
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Cumbernauld, townCentreOpening, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townCentreOpening Context triple: [Cumbernauld, townCentreOpening, 1967]
-
A.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
C.
culturalCenterOpened
Indicates that a cultural center has begun operating or officially opened at a certain time or place.
-
D.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
-
E.
municipalOfficesOpened
Indicates that municipal government offices have begun operating or have been officially opened for public service.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6786c880819088393bb107a7364c |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5fcf24348190b6b845205161c0ee |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:02 p.m.