Triple
T21604618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAM |
E533137
|
entity |
| Predicate | signifiesAppointmentAs |
P144751
|
FINISHED |
| Object | Member of the Order of Australia |
—
|
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: Member of the Order of Australia | Statement: [OAM, signifiesAppointmentAs, Member of the Order of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signifiesAppointmentAs Context triple: [OAM, signifiesAppointmentAs, Member of the Order of Australia]
-
A.
enabledAppointmentOf
Indicates that one entity made it possible or authorized for another entity to be appointed to a role or position.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
D.
appointmentTerm
Indicates the duration or specific period for which an appointment, position, or role is held.
-
E.
appointmentsInvolve
Indicates that scheduled appointments include or engage specific participants, resources, or activities in the appointment event.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e3e18c8190b9e0626c7d16805b |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:33 p.m.