Triple

T3557965
Position Surface form Disambiguated ID Type / Status
Subject Boaz E75264 entity
Predicate pairedWithFunctionally P50340 FINISHED
Object Jachin as twin pillar at temple entrance 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: Jachin as twin pillar at temple entrance | Statement: [Boaz, pairedWithFunctionally, Jachin as twin pillar at temple entrance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pairedWithFunctionally
Context triple: [Boaz, pairedWithFunctionally, Jachin as twin pillar at temple entrance]
  • A. parityWith
    Indicates that two entities share the same parity, such as both being even or both being odd.
  • B. dualPair
    Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
  • C. pairBond
    Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
  • D. endedFunctionallyWith
    Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
  • E. associatedWithMatch
    Indicates a relationship where an entity is linked or connected to a particular match or matching event.
  • 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_69ad85d45090819086f34fb85d850a1e completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc086e6688190b90ae356e18b953e completed March 8, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69adb834779081908468e182d5f6cf02 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb9bbb62c8190989629ca11733e1b completed March 8, 2026, 6:02 p.m.
Created at: March 8, 2026, 3:20 p.m.