Triple
T5210278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Officer of the Order of Australia |
E117613
|
entity |
| Predicate | usedAsTitleStyle |
P18055
|
FINISHED |
| Object | post-nominal only |
—
|
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: post-nominal only | Statement: [Officer of the Order of Australia, usedAsTitleStyle, post-nominal only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitleStyle Context triple: [Officer of the Order of Australia, usedAsTitleStyle, post-nominal only]
-
A.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
B.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
C.
includesTitleStyle
chosen
Indicates that one entity incorporates or specifies a particular style or formatting for a title associated with it.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for another entity.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a703e388190845dedd17252ddde |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.