Triple
T25372552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dis |
E632966
|
entity |
| Predicate | featuredInCanto |
P158476
|
FINISHED |
| Object | Inferno Canto VIII |
—
|
NE NERFINISHED |
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: Inferno Canto VIII | Statement: [Dis, featuredInCanto, Inferno Canto VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInCanto Context triple: [Dis, featuredInCanto, Inferno Canto VIII]
-
A.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
B.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
-
C.
enteredInCanto
chosen
Indicates that an entity appears or is mentioned within a specific canto of a larger poetic or literary work.
-
D.
featuredOnSong
Indicates that an entity (such as an artist) appears as a guest or secondary contributor on a particular song.
-
E.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 21, 2026, 1:38 p.m.