Triple
T14099997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet of Tasmania |
E339352
|
entity |
| Predicate | confidentialDeliberations |
P17107
|
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: [Cabinet of Tasmania, confidentialDeliberations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confidentialDeliberations Context triple: [Cabinet of Tasmania, confidentialDeliberations, true]
-
A.
deliberativeNature
Indicates that the action or process involves careful consideration, discussion, or weighing of options before reaching a decision.
-
B.
negotiatedInSecret
chosen
Indicates that the parties conducted negotiations privately, without public knowledge or disclosure.
-
C.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
D.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
-
E.
decisionsConcern
Indicates that certain decisions are about, relate to, or focus on a particular subject, issue, or 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fba7c10819095b1299b7b4f0310 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.