Triple
T15551780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victorian Legislative Council |
E370764
|
entity |
| Predicate | usesPartySystem |
P119141
|
FINISHED |
| Object | multi-party system |
—
|
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: multi-party system | Statement: [Victorian Legislative Council, usesPartySystem, multi-party system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPartySystem Context triple: [Victorian Legislative Council, usesPartySystem, multi-party system]
-
A.
usedInParty
Indicates that something is employed, involved, or utilized as part of a particular party or party-related event.
-
B.
usesPartyNominations
Indicates that one entity employs or relies on another entity’s party-based nominations in a selection or decision-making process.
-
C.
throwsPartyFor
Indicates that one entity organizes or hosts a party specifically for the benefit or honor of another entity.
-
D.
componentParty
Indicates that one party functions as a constituent or member of a larger party or group within a composite relationship.
-
E.
recognizesParty
Indicates that one entity formally acknowledges the existence, status, or legitimacy of another party.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:08 a.m.