Triple
T35849018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | תֻבָל |
E1036295
|
entity |
| Predicate | hasEthnonymRole |
P192095
|
FINISHED |
| Object | Eponymous ancestor of a people |
—
|
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: Eponymous ancestor of a people | Statement: [תֻבָל, hasEthnonymRole, Eponymous ancestor of a people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnonymRole Context triple: [תֻבָל, hasEthnonymRole, Eponymous ancestor of a people]
-
A.
hasEthnonymCountry
Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
-
B.
hasPrimaryEthnonym
Indicates that an entity is associated with its main or most commonly used ethnonym (ethnic group name) as its primary designation.
-
C.
isEthnonymFor
Indicates that one term is the ethnonym (name of a people or ethnic group) used to refer to another entity.
-
D.
hasEthnoreligiousRole
Indicates that an entity holds a role, function, or status defined by a combined ethnic and religious identity within a given context.
-
E.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.