Triple
T26337823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enten – Eller |
E662565
|
entity |
| Predicate | publishedInTwoVolumes |
P177292
|
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: [Enten – Eller, publishedInTwoVolumes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedInTwoVolumes Context triple: [Enten – Eller, publishedInTwoVolumes, true]
-
A.
hasSecondEditionNumberOfVolumes
Indicates that an entity’s second edition consists of a specified number of volumes.
-
B.
firstVolumesPublished
Indicates that the initial volumes of a multi-volume work have been published.
-
C.
publishedEdition
Indicates that one entity is a specific edition or version that has been formally published of another work or resource.
-
D.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
E.
publishedInPart
Indicates that a work or content item was released or made available only as a portion or installment within a larger publication or series.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 26, 2026, 10:37 p.m.