Triple
T12378961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apu Qun Tiqsi Wiraqutra |
E295696
|
entity |
| Predicate | honorificElementMeaning |
P102911
|
FINISHED |
| Object | lord |
—
|
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: lord | Statement: [Apu Qun Tiqsi Wiraqutra, honorificElementMeaning, lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificElementMeaning Context triple: [Apu Qun Tiqsi Wiraqutra, honorificElementMeaning, lord]
-
A.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
B.
honorificSuffixMeaning
chosen
Indicates that a particular honorific suffix conveys a specific meaning or nuance in how someone is addressed.
-
C.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
honorificStructure
Indicates a relationship where one entity’s title, form of address, or honorific expression is structurally linked to or derived from another entity within a formal naming or address system.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fb9eca48190aa6612ffc5ed0df2 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.