Triple
T23760421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Independence Day celebrations |
E587233
|
entity |
| Predicate | fireworksLocation |
P153859
|
FINISHED |
| Object | Charles River |
—
|
NE NERFINISHED |
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: Charles River | Statement: [Boston Independence Day celebrations, fireworksLocation, Charles River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireworksLocation Context triple: [Boston Independence Day celebrations, fireworksLocation, Charles River]
-
A.
fireworksDisplayDate
Indicates the date on which a fireworks display is scheduled to occur or took place.
-
B.
hasPyrotechnics
Indicates that an entity includes, uses, or features pyrotechnic effects or fireworks as part of its characteristics or activities.
-
C.
barrageLocation
Indicates the location where a barrage (such as an artillery or concentrated attack) is directed or occurs.
-
D.
balloonFestivalHeldIn
Indicates that a balloon festival takes place or is hosted at a specific location.
-
E.
locatedInFestival
Indicates that something exists or takes place within the spatial or organizational boundaries of a specific festival.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb1d6348190afb3f0fbea1b9ca3 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:14 p.m.