Triple
T15684241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemanja |
E380154
|
entity |
| Predicate | honorificUse |
P119748
|
FINISHED |
| Object | venerated in Serbian Orthodox Church |
—
|
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: venerated in Serbian Orthodox Church | Statement: [Nemanja, honorificUse, venerated in Serbian Orthodox Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificUse Context triple: [Nemanja, honorificUse, venerated in Serbian Orthodox Church]
-
A.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
hasHonorificSystem
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
-
D.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
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. 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:43 a.m.