Triple
T26345738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS filters |
E662772
|
entity |
| Predicate | computedValueType |
P61969
|
FINISHED |
| Object | list of filter functions |
—
|
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: list of filter functions | Statement: [CSS filters, computedValueType, list of filter functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computedValueType Context triple: [CSS filters, computedValueType, list of filter functions]
-
A.
typeOfValue
chosen
Indicates that one entity specifies the kind or category of value associated with another entity.
-
B.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
C.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
D.
exactValueKnownFor
Indicates that the precise, specific value of something is known and established for an entity in a given context.
-
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_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:42 p.m.