Triple
T27738069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatTable |
E697575
|
entity |
| Predicate | styleAPI |
P31951
|
FINISHED |
| Object | CSS classes |
—
|
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: CSS classes | Statement: [MatTable, styleAPI, CSS classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleAPI Context triple: [MatTable, styleAPI, CSS classes]
-
A.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
B.
styleContribution
Indicates a relationship where one entity contributes to or influences the stylistic characteristics or aesthetic qualities of another.
-
C.
styledAs
Indicates that one entity is presented, formatted, or designed in the manner, appearance, or aesthetic of another entity.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
APIStyle
chosen
Indicates a relationship where something conforms to, follows, or is characterized by a particular application programming interface (API) style or design convention.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 3:13 p.m.