Triple

T1716337
Position Surface form Disambiguated ID Type / Status
Subject Vixen E37297 entity
Predicate listedInLine P26405 FINISHED
Object "On, Comet! on, Cupid! on, Donder and Blitzen!" 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: "On, Comet! on, Cupid! on, Donder and Blitzen!" | Statement: [Vixen, listedInLine, "On, Comet! on, Cupid! on, Donder and Blitzen!"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: listedInLine
Context triple: [Vixen, listedInLine, "On, Comet! on, Cupid! on, Donder and Blitzen!"]
  • A. listedOn
    Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
  • B. inscriptionIncludesLine chosen
    Indicates that an inscription contains a specific line of text as one of its components.
  • C. isLinedWith
    Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
  • D. positionInProductLine
    Indicates the specific place or order an item occupies within a defined product line or series.
  • E. lineServed
    Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
  • 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_69a8861912dc8190931af43b4b9158a7 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab5c96db6c8190a745d6fef7bf2cdb completed March 6, 2026, 11 p.m.
PD Predicate disambiguation batch_69aa61bed2fc819086d912cd34285978 completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:30 p.m.