Triple
T21168347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Places |
E521628
|
entity |
| Predicate | expandedEditions |
P112178
|
FINISHED |
| Object | 1535 edition |
—
|
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: 1535 edition | Statement: [Common Places, expandedEditions, 1535 edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedEditions Context triple: [Common Places, expandedEditions, 1535 edition]
-
A.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
B.
expandedEditionYear
Indicates the year in which a work’s expanded or enlarged edition was published or released.
-
C.
expandedEditionContext
Indicates that one version of a work serves as an expanded edition of another, typically adding or extending content while preserving the original context.
-
D.
specialEdition
Indicates that an item is a distinct, limited, or enhanced version of a standard release, often with unique features, packaging, or content.
-
E.
laterEditions
chosen
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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72710c73881908d41aedff8984da9 |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.