Triple

T13776170
Position Surface form Disambiguated ID Type / Status
Subject Arycanda E331011 entity
Predicate hasMaterialEvidenceFrom P70490 FINISHED
Object Classical period 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: Classical period | Statement: [Arycanda, hasMaterialEvidenceFrom, Classical period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMaterialEvidenceFrom
Context triple: [Arycanda, hasMaterialEvidenceFrom, Classical period]
  • A. hasMaterialEvidence chosen
    Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
  • B. providesEvidenceFor
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • C. hasNoEvidenceOf
    Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
  • D. mayHearEvidenceFrom
    Indicates that an authority or decision-maker is permitted to receive and consider evidence presented by a specified source.
  • E. hasEvidentials
    Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0238bdbc8190a946e6e5431632a5 completed April 14, 2026, 9 a.m.
PD Predicate disambiguation batch_69dbbe97846c819093b00ea117b64e0d completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 10:10 p.m.