Triple
T3050217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Regions Module |
E83547
|
entity |
| Predicate | definesPseudoElement |
P38052
|
FINISHED |
| Object | ::region |
—
|
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: ::region | Statement: [CSS Regions Module, definesPseudoElement, ::region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPseudoElement Context triple: [CSS Regions Module, definesPseudoElement, ::region]
-
A.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
-
B.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
D.
definesSyntax
chosen
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
-
E.
definesPowersOf
Indicates that one entity specifies or determines the scope, limits, or nature of the authority or powers held by 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.