Triple
T7030544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway’s Doomsday algorithm |
E163256
|
entity |
| Predicate | hasReferenceDate |
P27895
|
FINISHED |
| Object | 4/4 (4 April) |
—
|
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: 4/4 (4 April) | Statement: [Conway’s Doomsday algorithm, hasReferenceDate, 4/4 (4 April)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceDate Context triple: [Conway’s Doomsday algorithm, hasReferenceDate, 4/4 (4 April)]
-
A.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
B.
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.
-
C.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
D.
hasCaptureDate
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.