Triple
T10781186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of Australia |
E254320
|
entity |
| Predicate | haveOwnPublicHolidays |
P95443
|
FINISHED |
| Object | state public holidays |
—
|
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: state public holidays | Statement: [States of Australia, haveOwnPublicHolidays, state public holidays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveOwnPublicHolidays Context triple: [States of Australia, haveOwnPublicHolidays, state public holidays]
-
A.
shareNationalHolidaysWith
Indicates that two entities observe the same set or a substantially overlapping set of national holidays.
-
B.
hasPublicDays
Indicates that an entity has specific days designated as open or accessible to the public.
-
C.
nationalHolidayCountry
Indicates that a specific day is officially recognized as a national holiday in a given country.
-
D.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
E.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c48c488190a2b3162202b74726 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.