Triple
T5568049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State and territory Australia Day councils |
E145927
|
entity |
| Predicate | eventDateFocus |
P46342
|
FINISHED |
| Object | 26 January |
—
|
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: 26 January | Statement: [State and territory Australia Day councils, eventDateFocus, 26 January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateFocus Context triple: [State and territory Australia Day councils, eventDateFocus, 26 January]
-
A.
eventFocus
Indicates that a particular event is the primary subject of attention, analysis, or relevance within a given context or dataset.
-
B.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
C.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
D.
eventStartDateOrganized
chosen
Indicates the date on which an event is formally scheduled or organized to begin.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0203789688190a0bab723186214ad |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.