Triple
T38673709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y2K |
E943669
|
entity |
| Predicate | criticalDate |
P191510
|
FINISHED |
| Object | 2000-01-01 |
—
|
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: 2000-01-01 | Statement: [Y2K, criticalDate, 2000-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticalDate Context triple: [Y2K, criticalDate, 2000-01-01]
-
A.
criticalTo
Indicates that one entity is essential or indispensable for the functioning, success, or existence of another entity.
-
B.
collapseDate
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
-
C.
timeCriticalFor
Indicates that one entity must occur, be addressed, or be completed within a strict or urgent time frame in relation to another entity or condition.
-
D.
criticalStrip
Indicates that something lies within the critical strip, the region of complex values whose real parts fall between 0 and 1.
-
E.
dateOfFirstCriticality
Indicates the date on which a nuclear reactor or system first achieved a self-sustaining nuclear chain reaction (first became critical).
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.