Triple
T36538832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Go for You |
E900659
|
entity |
| Predicate | performedAtEventType |
P80661
|
FINISHED |
| Object | benefit concert |
—
|
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: benefit concert | Statement: [I Go for You, performedAtEventType, benefit concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedAtEventType Context triple: [I Go for You, performedAtEventType, benefit concert]
-
A.
performedForEvent
Indicates that an action or service was carried out specifically in connection with, or on behalf of, a particular event.
-
B.
performedEvent
Indicates that an entity carried out, executed, or was responsible for a particular event.
-
C.
performedWhen
Indicates the specific time or temporal condition under which an action or event was carried out.
-
D.
appearsAtEventType
chosen
Indicates that an entity is present or participates in an event of a specified type.
-
E.
eventTypePerformedAt
Indicates that a specific type of event was carried out or occurred at a particular time or place.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.