Triple
T34955670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qemacs |
E1008116
|
entity |
| Predicate | supportsSearchAndReplace |
P206757
|
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: [qemacs, supportsSearchAndReplace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSearchAndReplace Context triple: [qemacs, supportsSearchAndReplace, true]
-
A.
replacesSupportFor
Indicates that one entity takes over or substitutes for the role or function previously provided by another entity’s support.
-
B.
replacesWord
Indicates that one word is substituted for another word in a given context or expression.
-
C.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
D.
renamingSupportedBy
Indicates that one entity provides the capability or functionality to perform renaming operations on another entity.
-
E.
replacesOrAlternativesTo
Indicates that one entity serves as a substitute for, or an alternative option to, another entity, potentially taking its place or offering a different choice.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.