Triple
T6572737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Asher |
E155479
|
entity |
| Predicate | roleInConquest |
P22409
|
FINISHED |
| Object | allocated territory in Book of 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: allocated territory in Book of Joshua | Statement: [Tribe of Asher, roleInConquest, allocated territory in Book of Joshua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInConquest Context triple: [Tribe of Asher, roleInConquest, allocated territory in Book of Joshua]
-
A.
roleDuringConquest
chosen
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
B.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
hasConqueringKing
Indicates that an entity has a king who has conquered or taken control over it or its territory.
-
E.
associatedWithMilitaryConquests
Indicates a relationship where an entity is connected to, involved in, or characterized by military conquests or campaigns.
- 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.