Triple
T35060467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معركة هرمجدون |
E1011576
|
entity |
| Predicate | تُستحضر_في |
P12313
|
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.
ذُكر_في
Indicates that an entity is mentioned or referenced within another entity, such as a text, document, or source.
-
B.
recalledBy
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
C.
recalledIn
chosen
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
-
D.
تعود_إلى
Indicates that something or someone returns, goes back, or is attributed back to a previous place, state, source, or reference.
-
E.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
- 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.