Triple
T24677927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barak |
E611041
|
entity |
| Predicate | ledAgainst |
P156962
|
FINISHED |
| Object | Sisera |
—
|
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: Sisera | Statement: [Barak, ledAgainst, Sisera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledAgainst Context triple: [Barak, ledAgainst, Sisera]
-
A.
ledAgainst
chosen
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
-
D.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
E.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:07 a.m.