Triple
T16223511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luria |
E393787
|
entity |
| Predicate | hasToponymicAssociation |
P122228
|
FINISHED |
| Object | families from Central and Eastern Europe |
—
|
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: families from Central and Eastern Europe | Statement: [Luria, hasToponymicAssociation, families from Central and Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToponymicAssociation Context triple: [Luria, hasToponymicAssociation, families from Central and Eastern Europe]
-
A.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
B.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
C.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
D.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
E.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
- F. None of above. chosen
Provenance (4 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d23e63881908806920d878f2adb |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.