Triple
T7205656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghazwat al‑Ahzab |
E148657
|
entity |
| Predicate | hasDefensiveWork |
P75813
|
FINISHED |
| Object | trench |
—
|
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: trench | Statement: [Ghazwat al‑Ahzab, hasDefensiveWork, trench]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefensiveWork Context triple: [Ghazwat al‑Ahzab, hasDefensiveWork, trench]
-
A.
defensiveTask
Indicates a task in which an entity protects, guards, or defends another entity or resource from potential threats or harm.
-
B.
hasDefenseStrategy
Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
-
C.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
D.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
E.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e94ef5cc81908c33adcedf5c5054 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8fd9b848190b2b1beea5698422b |
completed | March 27, 2026, 8:30 p.m. |
Created at: March 27, 2026, 2:52 p.m.