Triple
T9945745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardfile |
E195198
|
entity |
| Predicate | storageFormat |
P91294
|
FINISHED |
| Object | proprietary binary format |
—
|
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: proprietary binary format | Statement: [Cardfile, storageFormat, proprietary binary format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageFormat Context triple: [Cardfile, storageFormat, proprietary binary format]
-
A.
distributedFormat
Indicates that an entity is made available or disseminated in a particular format or medium.
-
B.
archiveFormat
Indicates the file format or type used to package or compress an archive.
-
C.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
D.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
E.
containerFormats
Indicates that one entity serves as a container or packaging format used to hold, encapsulate, or structure the contents of another entity.
- F. None of above. chosen
Provenance (4 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb655fba0819084a1e757b68c25d4 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:45 p.m.