Triple

T17062627
Position Surface form Disambiguated ID Type / Status
Subject oracular sanctuary of Apollo at Claros E413997 entity
Predicate consultationSetting P125712 FINISHED
Object subterranean chamber 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: subterranean chamber | Statement: [oracular sanctuary of Apollo at Claros, consultationSetting, subterranean chamber]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consultationSetting
Context triple: [oracular sanctuary of Apollo at Claros, consultationSetting, subterranean chamber]
  • A. consultationMethod
    Indicates the way or medium through which a consultation is conducted or delivered.
  • B. consultsOn
    Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
  • C. requiresConsultationWith
    Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
  • D. typicalAppointment
    Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
  • E. consulted
    Indicates that one entity sought advice, information, or guidance from 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_69d886cde3d481908d4d01ba88ba7eb7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3db7eb0808190ae1b0044e2b5cbd7 completed April 18, 2026, 7:29 p.m.
PD Predicate disambiguation batch_69e35d642f74819098c014135e249b27 completed April 18, 2026, 10:31 a.m.
PDg Predicate description generation batch_69e3753f93c88190808fec5692f66699 completed April 18, 2026, 12:12 p.m.
Created at: April 10, 2026, 5:34 a.m.