Triple

T112904
Position Surface form Disambiguated ID Type / Status
Subject Orthodox Judaism E2285 entity
Predicate recognizesAuthorityOf P2231 FINISHED
Object rabbinic authorities 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: rabbinic authorities | Statement: [Orthodox Judaism, recognizesAuthorityOf, rabbinic authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizesAuthorityOf
Context triple: [Orthodox Judaism, recognizesAuthorityOf, rabbinic authorities]
  • A. recognizedFor
    Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
  • B. hasAuthorityStatus chosen
    Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
  • C. recognizedRight
    Indicates that an agent formally acknowledges and accepts that another party possesses a specific right or entitlement.
  • D. recognizedIn
    Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
  • E. recognizedAs
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification 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_69a24fcdaeb48190a2d796677e4b3281 completed Feb. 28, 2026, 2:15 a.m.
NER Named-entity recognition batch_69a258808ff08190a06b6206f635612b completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a256425a488190959d71e39e699d90 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:20 a.m.