Triple
T31987354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puabi |
E816767
|
entity |
| Predicate | nameVariantStatus |
P19196
|
FINISHED |
| Object | Shubad is an obsolete reading of her name |
—
|
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: Shubad is an obsolete reading of her name | Statement: [Puabi, nameVariantStatus, Shubad is an obsolete reading of her name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameVariantStatus Context triple: [Puabi, nameVariantStatus, Shubad is an obsolete reading of her name]
-
A.
nameStatus
chosen
Indicates the status or condition associated with an entity’s name, such as whether it is current, preferred, alternate, or deprecated.
-
B.
nameHasVariant
Indicates that an entity’s name has an alternative or variant form.
-
C.
namesakeStatus
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
-
D.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
E.
familyNameStatus
Indicates the status or condition of a person's family name, such as whether it is current, former, changed, or otherwise designated.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b1cea8819087c59b8e8016fe6d |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:12 a.m.