Triple

T22805850
Position Surface form Disambiguated ID Type / Status
Subject Cananaean E564529 entity
Predicate isTraditionallyUnderstoodAs P39675 FINISHED
Object title indicating zeal 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: title indicating zeal | Statement: [Cananaean, isTraditionallyUnderstoodAs, title indicating zeal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTraditionallyUnderstoodAs
Context triple: [Cananaean, isTraditionallyUnderstoodAs, title indicating zeal]
  • A. isTraditionallyIdentifiedAs
    Indicates that one entity is customarily or historically recognized or labeled as being the same as, or corresponding to, another entity.
  • B. hasMeaningInOriginLanguage
    Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
  • C. canBeUnderstoodBy
    Indicates that something is comprehensible or interpretable to a particular entity or group.
  • D. traditionallyOneOf
    Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
  • E. hasTraditionalInterpretation chosen
    Indicates that something is associated with or understood according to a long-established or customary interpretation.
  • 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_69e245823f4c8190ade442cdcc2c224a completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d5c193481908550993e2547515d completed April 29, 2026, 3:39 a.m.
PD Predicate disambiguation batch_69eed2cb30f481909566369f515f6eff completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:32 p.m.