Triple
T35060498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منطقة تل مجيدو الأثرية |
E1011577
|
entity |
| Predicate | شهدت_معركة |
P11113
|
FINISHED |
| Object | معركة مجدو في عهد تحتمس الثالث |
—
|
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: معركة مجدو في عهد تحتمس الثالث | Statement: [منطقة تل مجيدو الأثرية, شهدت_معركة, معركة مجدو في عهد تحتمس الثالث]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: شهدت_معركة Context triple: [منطقة تل مجيدو الأثرية, شهدت_معركة, معركة مجدو في عهد تحتمس الثالث]
-
A.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
battleOccurred
chosen
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
E.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7860a1154819088c0faac06bc3852 |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.