Triple
T35249864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shibboleth incident |
E1018066
|
entity |
| Predicate | hasLeaderOnOneSide |
P40598
|
FINISHED |
| Object | Jephthah |
—
|
NE NERFINISHED |
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: Jephthah | Statement: [Shibboleth incident, hasLeaderOnOneSide, Jephthah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderOnOneSide Context triple: [Shibboleth incident, hasLeaderOnOneSide, Jephthah]
-
A.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
B.
hasMajorityLeader
Indicates that one entity serves as the primary or leading decision-making authority (majority leader) for another entity, typically within a governing or organizational body.
-
C.
hasLeaderParticipant
Indicates that an entity participates in an event or activity in the role of a leader.
-
D.
keyLeaderOnOneSide
chosen
Indicates that an entity serves as a primary or influential leader for one particular side or party within a conflict, competition, or division.
-
E.
hasLeaderAtLocation
Indicates that a specified leader is associated with or holds leadership responsibilities at a particular location.
- 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_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:02 p.m.