Triple

T880086
Position Surface form Disambiguated ID Type / Status
Subject Theatre of Delphi E19005 entity
Predicate builtInto P2012 FINISHED
Object hillside above the Temple of Apollo 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: hillside above the Temple of Apollo | Statement: [Theatre of Delphi, builtInto, hillside above the Temple of Apollo]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtInto
Context triple: [Theatre of Delphi, builtInto, hillside above the Temple of Apollo]
  • A. builtOn chosen
    Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
  • B. builtFrom
    Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
  • C. builtIn
    Indicates that one entity is inherently included as a standard, pre-existing component or feature of another entity, rather than being added or installed separately.
  • D. compiledIn
    Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
  • E. installedBy
    Indicates that one entity was set up, put in place, or made operational through the actions or intervention of 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_69a4939c32488190a7ccd41cf0abb22b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4acc9d5f4819087afbb75b6ac3dbf completed March 1, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69a4aa8d47c081909b02a53e305ccf7a completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.