Triple
T18954579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhein II |
E463737
|
entity |
| Predicate | editionIncludes |
P40815
|
FINISHED |
| Object | 1 artist’s proof |
—
|
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: 1 artist’s proof | Statement: [Rhein II, editionIncludes, 1 artist’s proof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionIncludes Context triple: [Rhein II, editionIncludes, 1 artist’s proof]
-
A.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
B.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
C.
includedInEdition
chosen
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
-
D.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
E.
editionWon
Indicates that a particular edition or instance of an event, competition, or award was won by a specified 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d546babc81909d4fc5b6b4441aac |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon