Triple
T1612544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Language Infrastructure |
E34643
|
entity |
| Predicate | definesAbbreviation |
P12874
|
FINISHED |
| Object | CTS for Common Type System |
—
|
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: CTS for Common Type System | Statement: [Common Language Infrastructure, definesAbbreviation, CTS for Common Type System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAbbreviation Context triple: [Common Language Infrastructure, definesAbbreviation, CTS for Common Type System]
-
A.
establishesAbbreviation
chosen
Indicates that one entity defines or introduces an abbreviated form that stands for another entity.
-
B.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
C.
notAbbreviationOf
Indicates that one term is explicitly asserted not to be an abbreviation or shortened form of another term.
-
D.
abbreviationOfRevision
Indicates that one revision serves as an abbreviated or shortened form of another, more complete revision.
-
E.
divisionAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of a division associated with 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.