Triple
T29405729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Calculator |
E745771
|
entity |
| Predicate | supportsRedo |
P204298
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GNOME Calculator, supportsRedo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRedo Context triple: [GNOME Calculator, supportsRedo, true]
-
A.
supportsUndo
Indicates that an action or operation can be reversed or undone after it has been performed.
-
B.
supportsRedundancy
Indicates that one entity provides or enables backup or failover capabilities for another to ensure continued operation if a primary component fails.
-
C.
canRevertTo
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
D.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
E.
supportsRewatch
Indicates that one entity allows or facilitates another entity being watched again after an initial viewing.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
| PDg | Predicate description generation | batch_6a036fb36c348190b56c005402b05f6c |
completed | May 12, 2026, 6:21 p.m. |
Created at: April 28, 2026, 2:54 p.m.