Triple
T23999106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epstein (Eppstein), Hesse, Germany |
E594192
|
entity |
| Predicate | isToponymicOriginOf |
P114931
|
FINISHED |
| Object | Jewish surname Epstein |
—
|
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 surname Epstein | Statement: [Epstein (Eppstein), Hesse, Germany, isToponymicOriginOf, Jewish surname Epstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isToponymicOriginOf Context triple: [Epstein (Eppstein), Hesse, Germany, isToponymicOriginOf, Jewish surname Epstein]
-
A.
hasOriginToponym
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
B.
hasCountryOfOriginToponym
Indicates that something has a place name (toponym) specifying the country from which it originates.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
usedAsToponymicBy
chosen
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
E.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d460b07881908ad11c03890ec1de |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:39 p.m.