Triple
T22979766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Multi-column Layout Module Level 1 |
E571425
|
entity |
| Predicate | definesShorthandFor |
P118797
|
FINISHED |
| Object | columns |
—
|
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: columns | Statement: [CSS Multi-column Layout Module Level 1, definesShorthandFor, columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesShorthandFor Context triple: [CSS Multi-column Layout Module Level 1, definesShorthandFor, columns]
-
A.
isShortForClass
Indicates that one class name is an abbreviation or shortened form of another class name.
-
B.
isShortenedVariantOf
chosen
Indicates that one form of an expression is a shortened or abbreviated version of another, longer form.
-
C.
canBeUsedWithAbbreviation
Indicates that one entity (such as a term, phrase, or expression) is suitable to be used together with a particular abbreviation.
-
D.
isShortFormOfMultiNames
Indicates that one term is a shortened or abbreviated form corresponding to multiple different full names.
-
E.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18294c4c8819083ef85d9cb736613 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.