Triple
T29405728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Calculator |
E745771
|
entity |
| Predicate | supportsUndo |
P204294
|
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, supportsUndo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUndo Context triple: [GNOME Calculator, supportsUndo, true]
-
A.
supportsHistory
Indicates that one entity provides assistance, endorsement, or foundational backing to another entity’s historical context, development, or continuity.
-
B.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
E.
supportsRefactoring
Indicates that one entity provides functionality or features that enable the other entity to perform or benefit from refactoring activities.
- 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_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
| PDg | Predicate description generation | batch_6a036f04c07c819099520ec48ee81461 |
completed | May 12, 2026, 6:18 p.m. |
Created at: April 28, 2026, 2:54 p.m.