Triple

T638982
Position Surface form Disambiguated ID Type / Status
Subject Plymouth Rock E16688 entity
Predicate linkedToMyth P9595 FINISHED
Object traditional but historically uncertain landing site 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: traditional but historically uncertain landing site | Statement: [Plymouth Rock, linkedToMyth, traditional but historically uncertain landing site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linkedToMyth
Context triple: [Plymouth Rock, linkedToMyth, traditional but historically uncertain landing site]
  • A. linkedToMythology chosen
    Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
  • B. mythologicalRole
    Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
  • C. mythologicalEvent
    Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
  • D. hasMythSource
    Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
  • E. otherDeity
    Indicates that one deity is distinct from and not identical to another deity within a given context or system.
  • 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_69a4936be1c88190af56540324b57da7 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a17b125481909a6ab53424954792 completed March 1, 2026, 8:28 p.m.
PD Predicate disambiguation batch_69a49d0629308190bcc137639567f7c2 completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.