Triple
T16018656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day of Reckoning |
E388536
|
entity |
| Predicate | isStandaloneReadable |
P92727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Day of Reckoning, isStandaloneReadable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandaloneReadable Context triple: [Day of Reckoning, isStandaloneReadable, true]
-
A.
isStandaloneFriendly
Indicates that an entity can operate or be used effectively on its own without requiring integration or support from other entities.
-
B.
isStandaloneWork
chosen
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
C.
isStandaloneRelease
Indicates that the release exists independently and is not part of a larger collection, series, or bundled set.
-
D.
canBeReadWith
Indicates that one entity is suitable or compatible to be read or interpreted together with another entity.
-
E.
canBeStandaloneName
Indicates that something is suitable to function independently as a complete, self-contained name without requiring additional qualifiers or context.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.