Triple

T26825723
Position Surface form Disambiguated ID Type / Status
Subject Cernunnos E675371 entity
Predicate sometimesComparedTo P161962 FINISHED
Object Herne the Hunter 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: Herne the Hunter | Statement: [Cernunnos, sometimesComparedTo, Herne the Hunter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sometimesComparedTo
Context triple: [Cernunnos, sometimesComparedTo, Herne the Hunter]
  • A. isComparedTo
    Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
  • B. comparisonType
    Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
  • C. oftenContrastedWith
    Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
  • D. comparisonReason
    Indicates that one entity is being compared to another specifically due to a stated reason, motive, or basis for the comparison.
  • E. hasComparison
    Indicates that one entity is being evaluated or contrasted relative to another entity based on some shared attribute or criterion.
  • 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_69eee9b6b28481909332f83eb17e5170 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f62081136c81909de8090b1d6c1ac5 completed May 2, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69f61b3d23f481908dfec27adace900a completed May 2, 2026, 3:41 p.m.
PDg Predicate description generation batch_69f61fd5442081908ca677a9c81dcb3f completed May 2, 2026, 4:01 p.m.
Created at: April 27, 2026, 4:58 a.m.