Triple
T35060236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ארמגדון |
E1011571
|
entity |
| Predicate | מיקום מסורתי |
P159479
|
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.
maMiejsceW
Indicates that something is located in or takes place within a specified place or context.
-
B.
luogo
chosen
Indicates that something is located, occurs, or exists in a particular place or location.
-
C.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
D.
locationSymbolic
Indicates a symbolic or abstract locational relationship between entities, where one is associated with a place or position in a non-literal, representational, or conceptual sense.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_69f78607679c819085c2e1fde23ed1ea |
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.