Triple
T35060472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معركة هرمجدون |
E1011576
|
entity |
| Predicate | تُفسَّر_أحيانًا_ك |
P2252
|
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.
interpretedInCase
chosen
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
B.
نوع_التفسير
Indicates the specific type or category of interpretation being applied to something.
-
C.
frequentlyInterpretedBy
Indicates that an entity is often or regularly interpreted, explained, or given meaning by a particular agent or group.
-
D.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
E.
intendedInterpretation
Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
- 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.