Triple
T25414237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore, County Waterford, Ireland |
E636784
|
entity |
| Predicate | patternDay |
P63429
|
FINISHED |
| Object | 24 July |
—
|
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: 24 July | Statement: [Ardmore, County Waterford, Ireland, patternDay, 24 July]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patternDay Context triple: [Ardmore, County Waterford, Ireland, patternDay, 24 July]
-
A.
pattern
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
B.
dayPattern
chosen
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
C.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
D.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
E.
shiftPattern
Indicates a recurring schedule or arrangement that defines how work or activity shifts are organized over time.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b010c50881909a6b77af88dd0579 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:55 p.m.