Triple

T25705762
Position Surface form Disambiguated ID Type / Status
Subject Longinus E644583 entity
Predicate nameTraditionallyGivenTo P17611 FINISHED
Object author of On the Sublime 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: author of On the Sublime | Statement: [Longinus, nameTraditionallyGivenTo, author of On the Sublime]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nameTraditionallyGivenTo
Context triple: [Longinus, nameTraditionallyGivenTo, author of On the Sublime]
  • A. namedAccordingTo
    Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
  • B. hasTraditionalName chosen
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • C. nameInWesternTradition
    Indicates that an entity’s name is expressed following Western naming conventions, typically with the given name preceding the family name.
  • D. unitNamesakeOf
    Indicates that a particular unit (such as an organization, division, or group) is named in honor of, or derives its name from, a specific entity.
  • E. birthNameMeaning
    Indicates the semantic meaning or significance associated with a person's birth name.
  • 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_69e77e83c8ec8190bf52fcdac4838984 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fc113b40819088a0d53c824097e4 completed May 2, 2026, 1:28 p.m.
PD Predicate disambiguation batch_69f4938262ac8190b41f922d0407d272 completed May 1, 2026, 11:50 a.m.
Created at: April 21, 2026, 9:04 p.m.