Triple
T26345940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Containment Module Level 1 |
E662776
|
entity |
| Predicate | definesValue |
P120595
|
FINISHED |
| Object | content-visibility: visible |
—
|
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: content-visibility: visible | Statement: [CSS Containment Module Level 1, definesValue, content-visibility: visible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesValue Context triple: [CSS Containment Module Level 1, definesValue, content-visibility: visible]
-
A.
valueDefinedBy
chosen
Indicates that the value of one entity is determined, specified, or constrained by another entity.
-
B.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
D.
defaultValue
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
E.
valueExpressed
Indicates that a particular value, opinion, or quantitative measure is articulated, represented, or made explicit by an entity or expression.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 26, 2026, 10:42 p.m.