Triple
T899353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Judges |
E19411
|
entity |
| Predicate | prologueContent |
P4446
|
FINISHED |
| Object | Israel’s failure to drive out the Canaanites |
—
|
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: Israel’s failure to drive out the Canaanites | Statement: [Book of Judges, prologueContent, Israel’s failure to drive out the Canaanites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prologueContent Context triple: [Book of Judges, prologueContent, Israel’s failure to drive out the Canaanites]
-
A.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
B.
primaryContent
chosen
Indicates that one entity serves as the main or most important content associated with another entity.
-
C.
includesSpokenPrologue
Indicates that an entity (such as a work or performance) contains a spoken introductory section delivered before the main content begins.
-
D.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
E.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.