Triple
T30420763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tk |
E773895
|
entity |
| Predicate | notableUserInterfaceStyle |
P46274
|
FINISHED |
| Object | Motif-like (historically) |
—
|
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: Motif-like (historically) | Statement: [Tk, notableUserInterfaceStyle, Motif-like (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUserInterfaceStyle Context triple: [Tk, notableUserInterfaceStyle, Motif-like (historically)]
-
A.
userInterfaceStyle
Indicates the visual presentation mode or theme (such as light or dark) that the user interface is currently using or configured to use.
-
B.
platformAppearance
Indicates how an entity is visually presented or styled on a particular platform or interface.
-
C.
notableStyleFeature
chosen
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
D.
navigationStyle
Indicates how an entity is configured or designed to guide movement, orientation, or traversal within a space or interface.
-
E.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:05 p.m.