Triple
T4740354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of Australia |
E105222
|
entity |
| Predicate | titleUsedInOath |
P48431
|
FINISHED |
| Object | Oath of Allegiance in 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: Oath of Allegiance in Australia | Statement: [Queen of Australia, titleUsedInOath, Oath of Allegiance in Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsedInOath Context triple: [Queen of Australia, titleUsedInOath, Oath of Allegiance in Australia]
-
A.
titleUsedInOaths
chosen
Indicates that a particular title is formally invoked or referenced within oaths or sworn declarations.
-
B.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
C.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
D.
oathAdministeredUnder
Indicates that an oath was formally given or imposed under the authority, conditions, or context of a specified person, body, or legal framework.
-
E.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6486f8608190908e43b777810c44 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.