Triple
T20255012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M (Australia) |
E498667
|
entity |
| Predicate | legallyBinding |
P110276
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [M (Australia), legallyBinding, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legallyBinding Context triple: [M (Australia), legallyBinding, false]
-
A.
legalSignificance
Indicates that something has recognized importance, effect, or consequence within a legal context or system.
-
B.
legalEmbodimentOf
Indicates that one entity serves as the legally recognized form, vehicle, or representation through which another entity exists, acts, or holds rights and obligations in law.
-
C.
hasLegalForceAs
chosen
Indicates that one thing possesses the binding legal effect or validity in the capacity or role of another specified thing.
-
D.
legalOrder
Indicates that an authoritative legal directive or mandate has been issued by a recognized legal body requiring specific actions or compliance from the involved parties.
-
E.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673ab60388190be32cc69bf2b6f76 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.