Triple
T1674786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP/M-86 |
E36205
|
entity |
| Predicate | fileNameConvention |
P1217
|
FINISHED |
| Object | 8.3 filename |
—
|
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: 8.3 filename | Statement: [CP/M-86, fileNameConvention, 8.3 filename]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileNameConvention Context triple: [CP/M-86, fileNameConvention, 8.3 filename]
-
A.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
B.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
C.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
D.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
E.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.