Triple

T31859108
Position Surface form Disambiguated ID Type / Status
Subject White Temple E813272 entity
Predicate builtForFunction P166435 FINISHED
Object religious worship 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: religious worship | Statement: [White Temple, builtForFunction, religious worship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtForFunction
Context triple: [White Temple, builtForFunction, religious worship]
  • A. isBuiltFor
    Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
  • B. structureBuiltFor chosen
    Indicates that one entity was constructed specifically to serve, house, or support the function, use, or needs of another entity.
  • C. isAlsoBuiltFor
    Indicates that something is additionally designed or constructed to serve another purpose, use, or type of entity beyond its primary one.
  • D. providesFunctionalityOf
    Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
  • E. implementedFor
    Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements 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_69f348ebf32881908d9439646933dc76 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b21e7e088190832a3db585daea1c completed May 3, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69f6b14faf608190a25b977c0740729c completed May 3, 2026, 2:22 a.m.
Created at: April 30, 2026, 11:52 p.m.