Triple
T3601421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Fortin |
E76263
|
entity |
| Predicate | hasLocalHoliday |
P31755
|
FINISHED |
| Object | Point Fortin Borough Day |
—
|
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: Point Fortin Borough Day | Statement: [Point Fortin, hasLocalHoliday, Point Fortin Borough Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalHoliday Context triple: [Point Fortin, hasLocalHoliday, Point Fortin Borough Day]
-
A.
hasRegionalHoliday
Indicates that a particular region observes or is associated with a specific holiday.
-
B.
hasMunicipalHoliday
chosen
Indicates that a particular place or jurisdiction observes a specific municipal holiday as part of its official local calendar.
-
C.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
D.
hasOfficialHoliday
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
-
E.
hasImportantHoliday
Indicates that an entity is associated with a holiday considered significant or special in some context.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1a1e8c48190a28ea3ddfe8c4e54 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.