Triple
T26345938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Containment Module Level 1 |
E662776
|
entity |
| Predicate | definesValueType |
P61969
|
FINISHED |
| Object | <contain-list> |
—
|
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: <contain-list> | Statement: [CSS Containment Module Level 1, definesValueType, <contain-list>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesValueType Context triple: [CSS Containment Module Level 1, definesValueType, <contain-list>]
-
A.
typeOfValue
chosen
Indicates that one entity specifies the kind or category of value associated with another entity.
-
B.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
C.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
D.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
E.
definesMessageType
Indicates that one entity specifies or determines the message type classification or category for 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 10:42 p.m.