Triple
T33515969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevurat ḥamor |
E858366
|
entity |
| Predicate | hasAuthorBirthPlaceRegion |
P21703
|
FINISHED |
| Object | Eastern Europe |
—
|
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: Eastern Europe | Statement: [Kevurat ḥamor, hasAuthorBirthPlaceRegion, Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorBirthPlaceRegion Context triple: [Kevurat ḥamor, hasAuthorBirthPlaceRegion, Eastern Europe]
-
A.
namedForPersonBornInArea
Indicates that something is named after a person who was born in the specified geographic area.
-
B.
creatorLivedIn
Indicates that the person who created a work resided in a particular place for some period of time.
-
C.
commemoratesPersonBirthRegion
Indicates that something serves to honor or mark the birthplace region of a specific person.
-
D.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
E.
allegedBirthRegion
chosen
Indicates the region where an entity is claimed or reported to have been born, without asserting that this birthplace is verified as fact.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:39 a.m.