Triple

T34775960
Position Surface form Disambiguated ID Type / Status
Subject McMinnville UFO photographs E1002505 entity
Predicate hasArchiveLocation P195869 FINISHED
Object various newspaper archives 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: various newspaper archives | Statement: [McMinnville UFO photographs, hasArchiveLocation, various newspaper archives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchiveLocation
Context triple: [McMinnville UFO photographs, hasArchiveLocation, various newspaper archives]
  • A. hasArchiveArea
    Indicates that an entity includes or is associated with a designated area used for archiving or long-term storage of materials.
  • B. archiveAvailability
    Indicates whether something is stored or accessible in an archive, and under what conditions it can be retrieved.
  • C. hasNotableArchive
    Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
  • D. hasSubArchive
    Indicates that one archive contains or includes another archive as a subordinate or nested component.
  • E. archiveFor
    Indicates that one entity serves as a storage or preservation repository specifically for the records, documents, or data of another entity.
  • F. None of above. chosen

Provenance (4 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_69f76db30a108190bb57ca95b873e5bb completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fdec5ffe088190ac5505f26c6cff18 completed May 8, 2026, 2 p.m.
PD Predicate disambiguation batch_69fdeae15f1c81908fc63fbc1b028d2e completed May 8, 2026, 1:53 p.m.
PDg Predicate description generation batch_69fdec5f0420819087c0230ad384c4ba completed May 8, 2026, 1:59 p.m.
Created at: May 3, 2026, 3:59 p.m.