Triple
T26532464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ka Erdy |
E670854
|
entity |
| Predicate | affectionateHonorific |
P167094
|
FINISHED |
| Object | Ka Erdy |
—
|
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: Ka Erdy | Statement: [Ka Erdy, affectionateHonorific, Ka Erdy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectionateHonorific Context triple: [Ka Erdy, affectionateHonorific, Ka Erdy]
-
A.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
-
B.
alternativeHonorificFor
Indicates that one honorific title can be used as an alternative form of address for another honorific.
-
C.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
D.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
E.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 1:36 a.m.