Triple
T35249788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | elders of Gilead |
E1018064
|
entity |
| Predicate | appointsAsCommander |
P1197
|
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: [elders of Gilead, appointsAsCommander, Jephthah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointsAsCommander Context triple: [elders of Gilead, appointsAsCommander, Jephthah]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
appointedAsCommanderInChief
Indicates that an entity is formally assigned the role and authority of commander-in-chief over a specified force, organization, or jurisdiction.
-
C.
dateAsActingCommander
Indicates the date on which an entity served in the role of acting commander.
-
D.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
E.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
- 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_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:02 p.m.