Triple
T35060492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منطقة تل مجيدو الأثرية |
E1011577
|
entity |
| Predicate | مرتبطة_بمصطلح |
P37
|
FINISHED |
| Object | هرمجدون |
—
|
NE NERFINISHED |
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.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
B.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
C.
meaningIsRelatedTo
Indicates that one concept has a semantic or contextual connection to another concept without specifying the exact nature of that relationship.
-
D.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
E.
phraseAssociation
Indicates an associative relationship where one phrase is linked, connected, or contextually related to another phrase.
- 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.