Triple
T37404494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hussam al-Din al-Jarrahi |
E929085
|
entity |
| Predicate | placeNamedAfterHim |
P87205
|
FINISHED |
| Object | Sheikh Jarrah |
—
|
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: Sheikh Jarrah | Statement: [Hussam al-Din al-Jarrahi, placeNamedAfterHim, Sheikh Jarrah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeNamedAfterHim Context triple: [Hussam al-Din al-Jarrahi, placeNamedAfterHim, Sheikh Jarrah]
-
A.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
B.
notablePlaceNamedAfter
Indicates that a notable place (such as a city, building, or landmark) is named in honor of or derived from the name of a particular entity.
-
C.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
-
D.
namedAfterCountryOfNamesake
Indicates that something is named after a person or entity whose own name is derived from a particular country.
-
E.
placeNamedAfterBy
chosen
Indicates that one entity serves as the namesake for a place, meaning the place is named after that 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:16 p.m.