Triple
T27730413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribbon interface |
E697415
|
entity |
| Predicate | supportsCustomizationVia |
P33710
|
FINISHED |
| Object | Ribbon XML |
—
|
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: Ribbon XML | Statement: [Ribbon interface, supportsCustomizationVia, Ribbon XML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCustomizationVia Context triple: [Ribbon interface, supportsCustomizationVia, Ribbon XML]
-
A.
hasCustomizationPotential
Indicates that an entity can be adapted, modified, or personalized beyond its default configuration.
-
B.
supportsPersonalization
Indicates that one entity enables or provides functionality for tailoring content, behavior, or experience to the preferences or characteristics of another entity.
-
C.
customizableBy
chosen
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
D.
hasCustomizationArea
Indicates that an entity includes or is associated with a specific area or section dedicated to customization or configuration.
-
E.
supportsUserSetups
Indicates that an entity provides functionality or compatibility for configurations or setups defined by the user.
- F. None of above.
Provenance (3 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: April 27, 2026, 3:11 p.m.