Triple
T14828386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambulance Service of New South Wales |
E348633
|
entity |
| Predicate | isStatutory |
P115994
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ambulance Service of New South Wales, isStatutory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStatutory Context triple: [Ambulance Service of New South Wales, isStatutory, true]
-
A.
hasStatuteLaw
Indicates that a jurisdiction or entity is governed by, or possesses, a body of formal written laws enacted by a legislative authority.
-
B.
statutoryType
Indicates the specific legal or statutory category under which something is formally classified or regulated.
-
C.
hasStatutes
Indicates that one entity possesses, is governed by, or is associated with a set of formal laws or statutes defined by another entity.
-
D.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
E.
statuteInterpreted
Indicates that a legal authority (such as a court or agency) has provided an interpretation or authoritative reading of a particular statute.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:51 a.m.