Triple
T18100892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn Gabirol Street, Tel Aviv |
E433210
|
entity |
| Predicate | namedAfterEthnicityOfEponym |
P41421
|
FINISHED |
| Object | Jewish |
—
|
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: Jewish | Statement: [Ibn Gabirol Street, Tel Aviv, namedAfterEthnicityOfEponym, Jewish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterEthnicityOfEponym Context triple: [Ibn Gabirol Street, Tel Aviv, namedAfterEthnicityOfEponym, Jewish]
-
A.
ethnicEponymOf
chosen
Indicates that one term is an eponym derived from or naming an ethnic group or people.
-
B.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
-
C.
hadEponymousAncestor
Indicates that an entity has an ancestor whose name it shares or from whom its own name is derived.
-
D.
eponymKnownFor
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
E.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb5e6208190b3c3cce3b95d66ad |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.