Triple
T29690396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCManFM |
E751194
|
entity |
| Predicate | supportsDragAndDropBetweenTabs |
P207172
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PCManFM, supportsDragAndDropBetweenTabs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDragAndDropBetweenTabs Context triple: [PCManFM, supportsDragAndDropBetweenTabs, yes]
-
A.
dragType
Indicates the manner or category of dragging interaction that occurs between entities.
-
B.
supportsMultipleWindows
Indicates that the subject can handle or display more than one window or view simultaneously.
-
C.
hasDropType
Indicates that an entity is associated with a specific type or category of drop (e.g., item, reward, or resource obtained).
-
D.
requiresToolForDrop
Indicates that performing a drop action on an entity necessitates the use of a specific tool.
-
E.
allowsChunkDropping
Indicates that an entity permits discarding or omitting data chunks, typically to reduce size or resource usage while accepting potential loss or degradation.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 28, 2026, 7:16 p.m.