Triple
T33810531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdulaziz |
E866517
|
entity |
| Predicate | hasHonorificConnotation |
P194094
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Abdulaziz, hasHonorificConnotation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorificConnotation Context triple: [Abdulaziz, hasHonorificConnotation, yes]
-
A.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
B.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address to another entity.
-
C.
honorificConnotation
Indicates that one entity refers to or characterizes another using an honorific or respectful form, conveying deference or elevated social status.
-
D.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
E.
hasHonorificDescription
Indicates that an entity is associated with an honorific title or descriptive phrase expressing respect or formal status.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:46 a.m.