Triple
T9651937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Style and Titles Act 1973 |
E233355
|
entity |
| Predicate | definesTitleOf |
P47620
|
FINISHED |
| Object | monarch 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: monarch of Australia | Statement: [Royal Style and Titles Act 1973, definesTitleOf, monarch of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTitleOf Context triple: [Royal Style and Titles Act 1973, definesTitleOf, monarch of Australia]
-
A.
definesHeadTitle
Indicates that one entity specifies or assigns the official head title or primary designation for another entity.
-
B.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
E.
providedTitle
chosen
Indicates that one entity has supplied or assigned a specific title or designation to 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bb0cce88190b7eacc8b43450d7f |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.