Triple
T24126002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missionary Oblates of Mary Immaculate |
E597801
|
entity |
| Predicate | honorificSuffixForMembers |
P341
|
FINISHED |
| Object | O.M.I. |
—
|
NE NERFINISHED |
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: O.M.I. | Statement: [Missionary Oblates of Mary Immaculate, honorificSuffixForMembers, O.M.I.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificSuffixForMembers Context triple: [Missionary Oblates of Mary Immaculate, honorificSuffixForMembers, O.M.I.]
-
A.
honorificSuffix
chosen
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
B.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
C.
honorificSuffixMeaning
Indicates that a particular honorific suffix conveys a specific meaning or nuance in how someone is addressed.
-
D.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
E.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee9086481909710c6d3291242c3 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.