Triple
T3860764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Naftali |
E90129
|
entity |
| Predicate | militaryEventDescribedIn |
P26327
|
FINISHED |
| Object | Judges 4 |
—
|
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: Judges 4 | Statement: [Tribe of Naftali, militaryEventDescribedIn, Judges 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryEventDescribedIn Context triple: [Tribe of Naftali, militaryEventDescribedIn, Judges 4]
-
A.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
B.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
C.
militaryCampaignsIn
Indicates that a military campaign took place within, or was conducted in, a specified geographic or political area.
-
D.
militaryConflictCovered
chosen
Indicates that one entity (such as a document, report, or media item) covers, describes, or reports on a specific military conflict involving another entity.
-
E.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec212a1c8190aba6311630c3fd3e |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.