Triple

T3830111
Position Surface form Disambiguated ID Type / Status
Subject Saxman Totem Park E90988 entity
Predicate hasInterpretiveElement P52235 FINISHED
Object guided tours 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: guided tours | Statement: [Saxman Totem Park, hasInterpretiveElement, guided tours]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInterpretiveElement
Context triple: [Saxman Totem Park, hasInterpretiveElement, guided tours]
  • A. hasInterpretiveSigns
    Indicates that interpretive or informational signs are present at or associated with the subject.
  • B. containsInterpretationOf
    Indicates that one entity includes or embodies an interpretation or understanding of another entity.
  • C. isInterpretedBy
    Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
  • D. hasLinguisticElement
    Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
  • E. hasInterpretiveExhibits
    Indicates that an entity includes or provides exhibits designed to explain, interpret, or contextualize information for viewers.
  • 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_69aed960b538819096561c8ed448dec9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeeb8459f881908a2c91bb07e381ef completed March 9, 2026, 3:47 p.m.
PD Predicate disambiguation batch_69aee74c2e04819094b94b3c0bac1806 completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aeeb828fb08190901d51edbe8bd304 completed March 9, 2026, 3:47 p.m.
Created at: March 9, 2026, 3:17 p.m.