Triple
T5260605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ai |
E118812
|
entity |
| Predicate | divineInstruction |
P62599
|
FINISHED |
| Object | battle plan revealed to Joshua |
—
|
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: battle plan revealed to Joshua | Statement: [Battle of Ai, divineInstruction, battle plan revealed to Joshua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineInstruction Context triple: [Battle of Ai, divineInstruction, battle plan revealed to Joshua]
-
A.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
B.
divineAgent
Indicates that the related entity acts as a deity or supernatural agent responsible for causing or overseeing the associated event or state.
-
C.
divineStatus
Indicates that an entity possesses a sacred, godlike, or religiously exalted status in relation to another entity or within a given belief system.
-
D.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
E.
divineFather
Indicates a paternal relationship in which one entity is regarded as the godly or divine father of another.
- F. None of above. chosen
Provenance (4 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.