Triple
T3050214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Regions Module |
E83547
|
entity |
| Predicate | definesSelector |
P45344
|
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, definesSelector, :region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSelector Context triple: [CSS Regions Module, definesSelector, :region]
-
A.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
B.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
C.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
D.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
E.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.