Triple
T29674504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Give Up 10th Anniversary Tour |
E750765
|
entity |
| Predicate | commemoratedWork |
P500
|
FINISHED |
| Object | Give Up |
—
|
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: Give Up | Statement: [Give Up 10th Anniversary Tour, commemoratedWork, Give Up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratedWork Context triple: [Give Up 10th Anniversary Tour, commemoratedWork, Give Up]
-
A.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another entity.
-
B.
commemoratedBy
chosen
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
C.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
D.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
E.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 7:07 p.m.