Triple
T7295533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian territories |
E164510
|
entity |
| Predicate | differFromStatesIn |
P21763
|
FINISHED |
| Object | representation in the Australian Parliament |
—
|
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: representation in the Australian Parliament | Statement: [Australian territories, differFromStatesIn, representation in the Australian Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differFromStatesIn Context triple: [Australian territories, differFromStatesIn, representation in the Australian Parliament]
-
A.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
B.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
C.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
D.
mayDifferFrom
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
E.
hasDifferentEnumerationsIn
chosen
Indicates that the same concept or item is represented with differing sets of enumeration values across the specified contexts or systems.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8d0c6c8190b32cd08b9a5d96cc |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.