Triple
T30970706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | minister general |
E789087
|
entity |
| Predicate | typicalHonorific |
P2097
|
FINISHED |
| Object | Very Reverend |
E490438
|
NE 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: Very Reverend | Statement: [minister general, typicalHonorific, Very Reverend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHonorific Context triple: [minister general, typicalHonorific, Very Reverend]
-
A.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
B.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
C.
honorificInitial
Indicates that one entity is the initial letter or abbreviated form of an honorific title used for another entity.
-
D.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
E.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
- F. None of above.
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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fbba1cb0819092a888ff69189861 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:54 p.m.