Triple
T29705761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Act 1915 |
E751623
|
entity |
| Predicate | passedByChamber |
P82767
|
FINISHED |
| Object | Australian House of Representatives |
—
|
NE NERFINISHED |
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: Australian House of Representatives | Statement: [Defence Act 1915, passedByChamber, Australian House of Representatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passedByChamber Context triple: [Defence Act 1915, passedByChamber, Australian House of Representatives]
-
A.
passedChamber
chosen
Indicates that a proposed measure or bill has been approved by a specific legislative chamber.
-
B.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
-
C.
passedHouseDate
Indicates the date on which a proposed measure or item was approved or passed by the House.
-
D.
passesBillsBy
Indicates that one entity successfully approves or enacts bills or legislation through the actions or decisions of another entity.
-
E.
passesBillsTo
Indicates that one entity formally transfers or submits bills or proposed legislation to another entity for consideration or action.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 7:27 p.m.