Triple

T5794959
Position Surface form Disambiguated ID Type / Status
Subject Pip’s Cave E128486 entity
Predicate hasTypeOfEvidence P3168 FINISHED
Object stone artifacts 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: stone artifacts | Statement: [Pip’s Cave, hasTypeOfEvidence, stone artifacts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypeOfEvidence
Context triple: [Pip’s Cave, hasTypeOfEvidence, stone artifacts]
  • A. usedEvidenceType chosen
    Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
  • B. providesEvidenceFor
    Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
  • C. hasEvidentials
    Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
  • D. hasNoEvidenceOf
    Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
  • E. hasGeneticEvidence
    Indicates that there is genetic data or analysis supporting the existence, validity, or nature of the specified relationship or association between entities.
  • 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_69c00845ca68819081a2ce3ecca577f7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02b1304588190b59a18fb7b70a60f completed March 22, 2026, 5:46 p.m.
PD Predicate disambiguation batch_69c021d477008190946113f9859eeb90 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:51 p.m.