Triple
T34955929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emacs diff-mode |
E1008121
|
entity |
| Predicate | hasCustomizationGroup |
P195870
|
FINISHED |
| Object | diff |
—
|
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: diff | Statement: [Emacs diff-mode, hasCustomizationGroup, diff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomizationGroup Context triple: [Emacs diff-mode, hasCustomizationGroup, diff]
-
A.
hasVariantGroup
Indicates that an entity is associated with a specific group of related variants that share common characteristics or classification.
-
B.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
C.
hasPlatformGroup
Indicates that an entity is associated with, or belongs to, a specific platform group.
-
D.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
E.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
- 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_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4 p.m.