Triple
T16117793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo permanent markers |
E391048
|
entity |
| Predicate | erasability |
P85615
|
FINISHED |
| Object | not dry-erasable |
—
|
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: not dry-erasable | Statement: [Expo permanent markers, erasability, not dry-erasable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erasability Context triple: [Expo permanent markers, erasability, not dry-erasable]
-
A.
erasesMemoriesOf
Indicates that one entity causes the memories of another entity to be removed or wiped out.
-
B.
reversibility
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
-
C.
removable
chosen
Indicates that one entity can be detached, taken off, or separated from another without causing damage or permanent alteration.
-
D.
attemptedToObliviate
Indicates that one entity tried, but did not necessarily succeed, to erase or alter another entity’s memory.
-
E.
palimpsest
Indicates that something has been reused or overwritten while still retaining traces or remnants of its earlier form or content.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016c10a081909b2d23ecea153a9c |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.