Triple
T26480574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrey Vasilyevich the Less |
E664670
|
entity |
| Predicate | honorificEpithets |
P155486
|
FINISHED |
| Object | the Less |
—
|
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: the Less | Statement: [Andrey Vasilyevich the Less, honorificEpithets, the Less]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificEpithets Context triple: [Andrey Vasilyevich the Less, honorificEpithets, the Less]
-
A.
honorificEpitet
chosen
Indicates that one entity is referred to or addressed using an honorific epithet, expressing respect, status, or reverence toward that entity.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
D.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
-
E.
honorificNature
Indicates that the relationship involves the use or assignment of an honorific title or respectful form of address between entities.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 12:26 a.m.