Triple

T897037
Position Surface form Disambiguated ID Type / Status
Subject Eleusinian Mysteries E19366 entity
Predicate possibleEarlierOrigins P1614 FINISHED
Object Mycenaean 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: Mycenaean period | Statement: [Eleusinian Mysteries, possibleEarlierOrigins, Mycenaean period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleEarlierOrigins
Context triple: [Eleusinian Mysteries, possibleEarlierOrigins, Mycenaean period]
  • A. earliestKnownAncestor
    Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
  • B. fossilRecordExtendsBackTo
    Indicates that the existence or presence of something is documented in the fossil record as originating from a specified time or geological period.
  • C. originSpecies
    Indicates that one entity is the original or source species from which another entity is derived, evolved, or produced.
  • D. hasHistoricalOrigin chosen
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • E. historicalOrigin
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad2550c88190a624eb5627d472ad completed March 1, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69a4aa9635608190a297e2067b8dcee2 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.