Triple

T5708708
Position Surface form Disambiguated ID Type / Status
Subject Carinish E125849 entity
Predicate hasHistoricPeriodEvidence P45898 FINISHED
Object Neolithic 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: Neolithic period | Statement: [Carinish, hasHistoricPeriodEvidence, Neolithic period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricPeriodEvidence
Context triple: [Carinish, hasHistoricPeriodEvidence, Neolithic period]
  • A. historicalEvidence chosen
    Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
  • B. historicalExistence
    Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
  • C. hasHistoryPeriod
    Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
  • D. hasNearbyHistoricPeriod
    Indicates that one historic period occurs close in time or space to another historic period.
  • E. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • 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_69c0082d6fe48190b777fb383769e5c8 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0248ab6a88190be17bdc32c36e5cb completed March 22, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69c021c2d8bc8190b947c7d1f423d2f3 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:46 p.m.