Triple
T31582584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Files-11 |
E805865
|
entity |
| Predicate | supportsNamingConvention |
P1217
|
FINISHED |
| Object | DEVICE:[DIRECTORY]FILENAME.EXT;VERSION |
—
|
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: DEVICE:[DIRECTORY]FILENAME.EXT;VERSION | Statement: [Files-11, supportsNamingConvention, DEVICE:[DIRECTORY]FILENAME.EXT;VERSION]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNamingConvention Context triple: [Files-11, supportsNamingConvention, DEVICE:[DIRECTORY]FILENAME.EXT;VERSION]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
C.
namespaceConvention
Indicates the naming and structural rules that govern how namespaces are defined, organized, and referenced in a system.
-
D.
namingConventionContext
Indicates the contextual rules or patterns that govern how something is named within a particular system or setting.
-
E.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:24 p.m.