Triple
T11957484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fvwm |
E284588
|
entity |
| Predicate | customizationLevel |
P33687
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [fvwm, customizationLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customizationLevel Context triple: [fvwm, customizationLevel, high]
-
A.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
B.
custom
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
-
C.
automationLevel
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
D.
configurationLevel
chosen
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
-
E.
brandingLevel
Indicates the degree or intensity of branding applied or associated with an entity (e.g., product, service, or organization).
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.