Triple
T9671526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogmanay celebrations |
E234040
|
entity |
| Predicate | continuesOn |
P89526
|
FINISHED |
| Object | 1 January |
—
|
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: 1 January | Statement: [Hogmanay celebrations, continuesOn, 1 January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesOn Context triple: [Hogmanay celebrations, continuesOn, 1 January]
-
A.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
B.
goesOn
Indicates that one entity participates in, boards, or travels using another entity, such as a vehicle, trip, or event.
-
C.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
D.
continuedOnNetwork
Indicates that an entity (such as a show, series, or program) remained in production or broadcast on the same network beyond a given point in time.
-
E.
hasContinuation
Indicates that one entity serves as a continuation or subsequent part of another entity in a sequence or process.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6949108190b699442e5c2aacf9 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.