Triple

T38228942
Position Surface form Disambiguated ID Type / Status
Subject The Old Rugged Cross E1012230 entity
Predicate invokesSymbol P108502 FINISHED
Object rugged wooden cross 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: rugged wooden cross | Statement: [The Old Rugged Cross, invokesSymbol, rugged wooden cross]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: invokesSymbol
Context triple: [The Old Rugged Cross, invokesSymbol, rugged wooden cross]
  • A. invocationOf
    Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
  • B. carriedSymbol
    Indicates that one entity physically or metaphorically bore, transported, or displayed a particular symbol.
  • C. invokesName
    Indicates that one entity calls or references another entity specifically by its name.
  • D. definesSymbol chosen
    Indicates that one entity specifies or establishes another entity as a symbol representing some concept, value, or object.
  • E. reverseSymbolizes
    Indicates that one entity serves as a symbolic representation of another, but in an inverse or opposite direction to the usual symbolism relationship.
  • 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_69f76dd25e0c81909f2abd0803e5e3ee completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc3321ef081908023590ba70ba0cf completed May 7, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69fcb0fdc6e08190b05e894c59481a0d completed May 7, 2026, 3:34 p.m.
Created at: May 3, 2026, 4:30 p.m.