Triple
T4264806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disco Demolition Night |
E96797
|
entity |
| Predicate | intendedActivity |
P48591
|
FINISHED |
| Object | public destruction of disco records |
—
|
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: public destruction of disco records | Statement: [Disco Demolition Night, intendedActivity, public destruction of disco records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedActivity Context triple: [Disco Demolition Night, intendedActivity, public destruction of disco records]
-
A.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
B.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
C.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
D.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
E.
associatedActivity
chosen
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcad0a881908e1cac0a6da5a321 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.