Triple
T29074009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sixth Column |
E735885
|
entity |
| Predicate | hasRevisedBookEdition |
P151743
|
FINISHED |
| Object | The Day After Tomorrow |
—
|
NE NERFINISHED |
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: The Day After Tomorrow | Statement: [Sixth Column, hasRevisedBookEdition, The Day After Tomorrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevisedBookEdition Context triple: [Sixth Column, hasRevisedBookEdition, The Day After Tomorrow]
-
A.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
B.
bookRevisionsBy
chosen
Indicates that one entity serves as the reviser or editor responsible for updating or modifying the content of a book.
-
C.
modernEditionBy
Indicates that one entity is a modern edition or updated version that has been prepared, edited, or published by another entity.
-
D.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
E.
laterEditions
Indicates that one entity is a subsequent or more recent edition of another entity.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 28, 2026, 10:21 a.m.