Triple
T30501307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الشرقاط |
E776142
|
entity |
| Predicate | تشتهر بـ |
P161540
|
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 someone or something became well-known or famous specifically because of a particular story.
-
B.
bekanntFür
chosen
Indicates that one entity is known or recognized for a particular quality, achievement, work, or characteristic associated with another entity.
-
C.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
شهرت اصلی
Indicates a primary or most notable form of fame or recognition associated with an entity.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687805b048190824b5c0bc8d09bab |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:14 p.m.