Triple
T26829538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Devoted Friend |
E675459
|
entity |
| Predicate | includedInCollectionPublicationYear |
P97077
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [The Devoted Friend, includedInCollectionPublicationYear, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInCollectionPublicationYear Context triple: [The Devoted Friend, includedInCollectionPublicationYear, 1888]
-
A.
collectedInPublicationYear
Indicates that the collecting event or data record was documented in a publication that appeared in the specified year.
-
B.
laterCollectionPublicationYear
Indicates that the referenced collection was published in a year later than the year associated with the compared collection or work.
-
C.
appearsInPublicationYear
chosen
Indicates that an entity is featured in a publication that was released in a specific year.
-
D.
originalCollectionPublicationYear
Indicates the year in which the original collection containing the entity was first published.
-
E.
catalogueInclusionYear
Indicates the year in which an item was first included or recorded in a catalogue.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 27, 2026, 5 a.m.