Triple
T12102259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian state and territory elections |
E288218
|
entity |
| Predicate | arePeriodic |
P7407
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Australian state and territory elections, arePeriodic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arePeriodic Context triple: [Australian state and territory elections, arePeriodic, true]
-
A.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
B.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
C.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
D.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
E.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.