Triple

T35249877
Position Surface form Disambiguated ID Type / Status
Subject Shibboleth incident E1018066 entity
Predicate hasNumberKilledAccordingToText P25362 FINISHED
Object 42000 Ephraimites 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: 42000 Ephraimites | Statement: [Shibboleth incident, hasNumberKilledAccordingToText, 42000 Ephraimites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNumberKilledAccordingToText
Context triple: [Shibboleth incident, hasNumberKilledAccordingToText, 42000 Ephraimites]
  • A. killedApproximate chosen
    Indicates that one entity caused the death of another, but the information about this killing is uncertain, estimated, or not known with exact precision.
  • B. isKilledTo
    Indicates that one entity is killed as a consequence or objective of an action performed by another entity.
  • C. killedDuring
    Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
  • D. numberOfConfirmedKills
    Indicates the total count of individuals that an entity is reported or confirmed to have killed.
  • E. killedBecauseOf
    Indicates that one entity killed another specifically due to a particular reason, motive, or triggering factor associated with that other entity or a related circumstance.
  • 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_69f76de407d081909dfc3c419817ae93 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fed6da0390819096b88ef4714b144e completed May 9, 2026, 6:40 a.m.
PD Predicate disambiguation batch_69fed53517d081909966f31707625f1a completed May 9, 2026, 6:33 a.m.
Created at: May 3, 2026, 4:02 p.m.