Triple
T17055861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deputy Premier of New South Wales |
E413816
|
entity |
| Predicate | usuallyHolds |
P39152
|
FINISHED |
| Object | major ministerial portfolio |
—
|
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: major ministerial portfolio | Statement: [Deputy Premier of New South Wales, usuallyHolds, major ministerial portfolio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usuallyHolds Context triple: [Deputy Premier of New South Wales, usuallyHolds, major ministerial portfolio]
-
A.
typicallyHolds
chosen
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
-
B.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
C.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
D.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
E.
canBeHeldIn
Indicates that one entity is capable of being contained, hosted, or conducted within another 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7934e881909e9f0ae956fb0816 |
completed | April 18, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.