Triple
T21423947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore 1541 |
E528504
|
entity |
| Predicate | hasDataEncoding |
P33682
|
FINISHED |
| Object | group coded recording |
—
|
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: group coded recording | Statement: [Commodore 1541, hasDataEncoding, group coded recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataEncoding Context triple: [Commodore 1541, hasDataEncoding, group coded recording]
-
A.
dataEncodingMethod
chosen
Indicates the specific technique or format used to encode data for storage, transmission, or processing.
-
B.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
C.
hasMIMECharsetName
Indicates that an entity (such as a character encoding) is associated with a specific MIME charset name used in internet protocols.
-
D.
hasDataFile
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
-
E.
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.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813b798c8190a379cbf6cc6e14d2 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.