Triple
T34623167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Court of Western Australia |
E889060
|
entity |
| Predicate | canMakeOrders |
P179709
|
FINISHED |
| Object | parenting orders |
—
|
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: parenting orders | Statement: [Family Court of Western Australia, canMakeOrders, parenting orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canMakeOrders Context triple: [Family Court of Western Australia, canMakeOrders, parenting orders]
-
A.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
B.
canCallToOrder
Indicates that one entity has the authority or ability to formally initiate or restore order in a meeting, session, or assembly involving another entity.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
recognizesOrders
Indicates that one entity formally acknowledges and accepts the orders or directives issued by another entity.
-
E.
canOrderNewTrial
Indicates that an authority (typically a court or judge) has the legal power to initiate or grant a new trial in a case.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:04 a.m.