Triple
T5026534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrate Brooklyn! Festival |
E113188
|
entity |
| Predicate | benefitConcertsSupport |
P60593
|
FINISHED |
| Object | free programming |
—
|
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: free programming | Statement: [Celebrate Brooklyn! Festival, benefitConcertsSupport, free programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitConcertsSupport Context triple: [Celebrate Brooklyn! Festival, benefitConcertsSupport, free programming]
-
A.
concertsFreeOfCharge
Indicates that the concerts are held without requiring attendees to pay an admission fee.
-
B.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
-
C.
associatedWithSupportersSong
Indicates that there is a relationship between an entity and a supporters’ song, such as being linked to, represented by, or commonly accompanied by that song.
-
D.
usedBySupporters
Indicates that something is utilized or employed by supporters of a person, group, cause, or entity.
-
E.
benefitsCause
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or cause.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738c3aac81908fb6a5c70c97a394 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.