Triple
T22749675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilted Arc |
E562658
|
entity |
| Predicate | cannotBeReinstalled |
P149601
|
FINISHED |
| Object | artist considers work destroyed if moved |
—
|
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: artist considers work destroyed if moved | Statement: [Tilted Arc, cannotBeReinstalled, artist considers work destroyed if moved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeReinstalled Context triple: [Tilted Arc, cannotBeReinstalled, artist considers work destroyed if moved]
-
A.
cannotBeUninstalled
Indicates that the specified entity cannot be removed or uninstalled from the system or environment.
-
B.
cannotBeRemovedBy
Indicates that one entity is not capable of removing, deleting, or otherwise eliminating another entity.
-
C.
cannotRevoke
Indicates that a previously granted permission, status, or action cannot be withdrawn, canceled, or undone.
-
D.
cannotChange
Indicates that an entity is unable or not permitted to alter the state, value, or properties of another entity or relationship.
-
E.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b822988190b5368ac1f4e1d70a |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:24 p.m.