Triple
T34021273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Āryadeva |
E872387
|
entity |
| Predicate | honorificTitleInTibet |
P2097
|
FINISHED |
| Object | ’Phags pa Lha (Aryadeva) |
—
|
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: ’Phags pa Lha (Aryadeva) | Statement: [Āryadeva, honorificTitleInTibet, ’Phags pa Lha (Aryadeva)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificTitleInTibet Context triple: [Āryadeva, honorificTitleInTibet, ’Phags pa Lha (Aryadeva)]
-
A.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
B.
honorificTitleInChinese
Indicates that one entity is the honorific or respectful title used in Chinese to refer to another entity.
-
C.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
-
D.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
E.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:51 a.m.