Triple
T29405719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Calculator |
E745771
|
entity |
| Predicate | hasModeSwitching |
P192141
|
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, hasModeSwitching, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeSwitching Context triple: [GNOME Calculator, hasModeSwitching, true]
-
A.
hasModeSystem
Indicates that one entity operates under, or is associated with, a particular mode defined or managed by another system.
-
B.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
C.
hasInteractionMode
Indicates the way in which two entities engage or interact with each other, specifying the manner, channel, or pattern of their interaction.
-
D.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
E.
hasSwitchColor
Indicates that an entity possesses or is associated with a switch whose color is specified.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 28, 2026, 2:54 p.m.