Triple
T35060443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | معركة هرمجدون |
E1011576
|
entity |
| Predicate | ذات_طبيعة |
P2435
|
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.
hasNature
chosen
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
B.
relatesToNatureOf
Indicates a general relationship that concerns or characterizes the inherent nature, essence, or fundamental qualities of something.
-
C.
binaryNatureRevealedBy
Indicates that the dual or two-part nature of something becomes apparent or is made known through a specified source, process, or evidence.
-
D.
digitalNature
Indicates a relationship where something exists, operates, or is characterized primarily in a digital or computational form rather than a physical or analog one.
-
E.
natureIsClearlyDefined
Indicates that the inherent characteristics, boundaries, or essential qualities of something are explicitly and unambiguously specified.
- 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.