Triple
T33432120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Etymologies |
E856156
|
entity |
| Predicate | firstPublicationVolume |
P52479
|
FINISHED |
| Object | The History of Middle-earth, Volume 5 |
E264397
|
NE 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: The History of Middle-earth, Volume 5 | Statement: [The Etymologies, firstPublicationVolume, The History of Middle-earth, Volume 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationVolume Context triple: [The Etymologies, firstPublicationVolume, The History of Middle-earth, Volume 5]
-
A.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
B.
firstVolumesPublished
chosen
Indicates that the initial volumes of a multi-volume work have been published.
-
C.
firstSerialPublicationYear
Indicates the calendar year in which a work was first published in serial form.
-
D.
firstPublicationOpus
Indicates that the linked work is the first published opus (or first formally published work) of the associated creator or entity.
-
E.
initialPublication
Indicates the relationship in which a work is first formally published or made publicly available.
- F. None of above.
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803e4b2c08190abfd7190dcb9f985 |
completed | June 21, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.