Triple
T943457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitzevet bat Adael |
E20357
|
entity |
| Predicate | hasPatronymic |
P7966
|
FINISHED |
| Object | bat Adael |
—
|
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: bat Adael | Statement: [Nitzevet bat Adael, hasPatronymic, bat Adael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronymic Context triple: [Nitzevet bat Adael, hasPatronymic, bat Adael]
-
A.
patronymicName
chosen
Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
-
B.
hasPostnominalLetters
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
C.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
D.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
E.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a2b1ec8190a2753ad3b3e8cc7a |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.