Triple
T9931564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKCS #8 |
E192658
|
entity |
| Predicate | commonlyEncodedAs |
P1444
|
FINISHED |
| Object | PEM |
—
|
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: PEM | Statement: [PKCS #8, commonlyEncodedAs, PEM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyEncodedAs Context triple: [PKCS #8, commonlyEncodedAs, PEM]
-
A.
commonlyAssociatedCodec
Indicates that one item is typically linked or paired with a particular codec in common usage or practice.
-
B.
encodedIn
chosen
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
C.
notEncodedIn
Indicates that a piece of information, data, or content is explicitly absent from or not represented within a given encoding, format, or medium.
-
D.
encodedInUnicodeSince
Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
-
E.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.