Triple
T237480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New South Wales Legislative Council |
E4852
|
entity |
| Predicate | canRejectBills |
P9445
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [New South Wales Legislative Council, canRejectBills, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRejectBills Context triple: [New South Wales Legislative Council, canRejectBills, yes]
-
A.
canDelayMoneyBillsFor
Indicates that one entity has the authority or ability to postpone or extend the payment deadline of money-related bills for another entity.
-
B.
canMandate
Indicates that one entity has the authority or power to require another entity to perform or comply with something.
-
C.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b5f27208190ae13f34037fe582b |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25dab745c8190829b7b5e915936e8 |
completed | Feb. 28, 2026, 3:14 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.