Triple

T26138296
Position Surface form Disambiguated ID Type / Status
Subject معبد بتاح في منف E659441 entity
Predicate كان تحت رعاية P9459 FINISHED
Object كهنة بتاح في منف 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: كهنة بتاح في منف | Statement: [معبد بتاح في منف, كان تحت رعاية, كهنة بتاح في منف]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: كان تحت رعاية
Context triple: [معبد بتاح في منف, كان تحت رعاية, كهنة بتاح في منف]
  • A. underAuspicesOf chosen
    Indicates that an action, event, or entity operates under the sponsorship, authority, or guidance of another party.
  • B. endedUnderAdministration
    Indicates that an entity’s existence, operation, or status concluded while it was under the control or management of a particular administrative authority.
  • C. wasHeldUnder
    Indicates that an event, activity, or state took place while being subject to the authority, control, jurisdiction, or auspices of a particular entity or condition.
  • D. tookCareOf
    Indicates that one entity provided care, support, or maintenance for another entity over a period of time.
  • E. underSafeguardsOf
    Indicates that one entity is protected, regulated, or controlled by the safety measures, oversight, or protective mechanisms established by 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_69ee5bc3c20c8190bf2cf272f4170e95 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f60be1d2408190820365bf7d8436bd completed May 2, 2026, 2:36 p.m.
PD Predicate disambiguation batch_69f5b0021da88190bdd4cf2698c23edf completed May 2, 2026, 8:04 a.m.
Created at: April 26, 2026, 8:18 p.m.