Triple
T25443192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomsday of a year |
E637559
|
entity |
| Predicate | hasAnchorDate |
P27895
|
FINISHED |
| Object | December 12 |
—
|
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: December 12 | Statement: [Doomsday of a year, hasAnchorDate, December 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnchorDate Context triple: [Doomsday of a year, hasAnchorDate, December 12]
-
A.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
B.
hasAnchorLocation
Indicates that one entity serves as the fixed reference or attachment point (anchor) for the location or position of another entity.
-
C.
hasBaseDate
chosen
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
D.
hasPrimaryAnchor
Indicates that one entity serves as the main or principal anchor or reference point for another entity.
-
E.
holdingDate
Indicates the date on which a holding, possession, or ownership of something is recorded or takes effect.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2 p.m.