Triple
T12743571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eaton’s |
E304546
|
entity |
| Predicate | catalogueFirstIssued |
P106676
|
FINISHED |
| Object | 1884 |
—
|
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: 1884 | Statement: [Eaton’s, catalogueFirstIssued, 1884]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueFirstIssued Context triple: [Eaton’s, catalogueFirstIssued, 1884]
-
A.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
B.
firstCollectedEditionYear
Indicates the year in which the first collected edition of a work was published or made available.
-
C.
firstFasciclesPublished
Indicates that the subject is the entity for which the earliest fascicles (initial installments or parts of a larger work) were published.
-
D.
printedFirstEditionOf
Indicates that the subject entity produced and issued the initial published edition of the object entity.
-
E.
firstIssueCoverDate
Indicates the date on which the first issue of something (such as a series, publication, or comic) was initially released or covered.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.