Triple

T20083042
Position Surface form Disambiguated ID Type / Status
Subject Eglon E500049 entity
Predicate subsequentRole P138651 FINISHED
Object example of divine deliverance through judge 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: example of divine deliverance through judge | Statement: [Eglon, subsequentRole, example of divine deliverance through judge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subsequentRole
Context triple: [Eglon, subsequentRole, example of divine deliverance through judge]
  • A. successorRole
    Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
  • B. successorStateRole
    Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
  • C. successorInSomeRoles
    Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
  • D. roleAfterConversion
    Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
  • E. successionRole
    Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
  • 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6655946f48190a6b4cb13ea4e212a completed April 20, 2026, 5:41 p.m.
PD Predicate disambiguation batch_69e54cf369b88190931532420517dac7 completed April 19, 2026, 9:45 p.m.
PDg Predicate description generation batch_69e54fc20888819083c9118a09d0d2dc completed April 19, 2026, 9:57 p.m.
Created at: April 11, 2026, 3:41 p.m.