Triple
T33850130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Honiara |
E867598
|
entity |
| Predicate | officialStyle |
P134513
|
FINISHED |
| Object | Your Grace |
—
|
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: Your Grace | Statement: [Archbishop of Honiara, officialStyle, Your Grace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialStyle Context triple: [Archbishop of Honiara, officialStyle, Your Grace]
-
A.
hasOfficialStyle
chosen
Indicates that an entity possesses a formally recognized style, manner, or form as defined by an authoritative source or standard.
-
B.
governsInStyle
Indicates that a governing entity exercises authority or leadership in a distinctive, notable, or characteristic manner.
-
C.
majorStyleAlongWith
Indicates that one style is a primary or major style that occurs together with another associated style.
-
D.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
E.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 1, 2026, 1:47 a.m.