Triple

T29037019
Position Surface form Disambiguated ID Type / Status
Subject Temple of Apollo Epicurius E737887 entity
Predicate protectionStructure P8412 FINISHED
Object protective tent shelter 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: protective tent shelter | Statement: [Temple of Apollo Epicurius, protectionStructure, protective tent shelter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protectionStructure
Context triple: [Temple of Apollo Epicurius, protectionStructure, protective tent shelter]
  • A. infrastructureProtected
    Indicates that infrastructure is safeguarded or defended against damage, disruption, or unauthorized interference.
  • B. defensiveStructure chosen
    Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
  • C. shareDefenseStructure
    Indicates that two or more entities utilize or are protected by the same defensive structure or system.
  • D. isFortifiedStructureOf
    Indicates that one entity is a defensive or fortified structure that protects, encloses, or is associated with another entity.
  • E. guardedStructure
    Indicates that a structure is being protected or watched over by a guarding entity or mechanism.
  • 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_69f077efb3848190b41574e1670f6ae2 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 28, 2026, 9:59 a.m.