Triple
T10329302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Fullscreen Module Level 1 |
E242835
|
entity |
| Predicate | definesPseudoClass |
P45344
|
FINISHED |
| Object | :fullscreen |
—
|
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: :fullscreen | Statement: [CSS Fullscreen Module Level 1, definesPseudoClass, :fullscreen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPseudoClass Context triple: [CSS Fullscreen Module Level 1, definesPseudoClass, :fullscreen]
-
A.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
B.
definesSelector
chosen
Indicates that one entity specifies or determines the selection criteria used to choose or identify another entity.
-
C.
predicateOf
Indicates that one entity functions as a predicate or predicative expression that attributes a property, relation, or condition to another entity.
-
D.
definesComponent
Indicates that one entity specifies or establishes the structure, behavior, or characteristics of another entity as its component.
-
E.
definesElement
Indicates that one entity specifies or determines the nature, structure, or identity of another entity as its defining element.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.