Triple

T37514496
Position Surface form Disambiguated ID Type / Status
Subject Ruined Temple E932599 entity
Predicate environmentState P2900 FINISHED
Object Ruined 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: Ruined | Statement: [Ruined Temple, environmentState, Ruined]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: environmentState
Context triple: [Ruined Temple, environmentState, Ruined]
  • A. environmentType
    Indicates the kind or category of environment associated with an entity or situation.
  • B. environmentalCondition chosen
    Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
  • C. environmentClass
    Indicates that an entity belongs to, or is categorized within, a particular type or class of environment.
  • D. environmentAnalogOf
    Indicates that one environment serves as an analogue or counterpart to another, typically mirroring its conditions, structure, or behavior for comparison or simulation purposes.
  • E. environs
    Indicates that one entity surrounds, encircles, or lies all around another entity in space.
  • 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_69f76ec730988190b5aa4f9cb9afd518 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbacaf54648190811ea33b34907e8e completed May 6, 2026, 9:03 p.m.
PD Predicate disambiguation batch_69fba883f770819091059c6f6c6af9f7 completed May 6, 2026, 8:45 p.m.
Created at: May 3, 2026, 4:17 p.m.