Triple
T16747348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEng |
E406989
|
entity |
| Predicate | typicalAbbreviationStyle |
P24474
|
FINISHED |
| Object | capital C followed by capital E, n, g |
—
|
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: capital C followed by capital E, n, g | Statement: [CEng, typicalAbbreviationStyle, capital C followed by capital E, n, g]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAbbreviationStyle Context triple: [CEng, typicalAbbreviationStyle, capital C followed by capital E, n, g]
-
A.
abbreviationStyle
chosen
Indicates the specific way in which something is abbreviated, such as the format, punctuation, or capitalization used in its shortened form.
-
B.
typeOfAbbreviation
Indicates that one term is an abbreviation of a specific type or category (e.g., acronym, initialism) of another expression.
-
C.
isCommonAbbreviation
Indicates that one term is a widely used shortened or abbreviated form of another term.
-
D.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
E.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2439848190a86a5bfc0702e2fe |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.