Triple
T8917991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mintBackup |
E212339
|
entity |
| Predicate | backupFormat |
P82525
|
FINISHED |
| Object | compressed archive |
—
|
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: compressed archive | Statement: [mintBackup, backupFormat, compressed archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupFormat Context triple: [mintBackup, backupFormat, compressed archive]
-
A.
supportsBackupFormat
chosen
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
B.
archiveFormat
Indicates the file format or type used to package or compress an archive.
-
C.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.