Triple
T104826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Patrick’s Day Parade (New York City) |
E2116
|
entity |
| Predicate | typicalDayAssociatedWith |
P4563
|
FINISHED |
| Object | March 17 |
—
|
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: March 17 | Statement: [St. Patrick’s Day Parade (New York City), typicalDayAssociatedWith, March 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDayAssociatedWith Context triple: [St. Patrick’s Day Parade (New York City), typicalDayAssociatedWith, March 17]
-
A.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
observesDay
chosen
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
-
D.
typicalBackground
Indicates that an entity has a usual or commonly expected background, context, or setting associated with it.
-
E.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.