Triple
T4600105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyISAM storage engine |
E100301
|
entity |
| Predicate | filePerTable |
P33527
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MyISAM storage engine, filePerTable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filePerTable Context triple: [MyISAM storage engine, filePerTable, true]
-
A.
dataFile
Indicates a relationship where one entity serves as or is associated with a specific data file used, stored, or referenced by another entity.
-
B.
fileManagementModel
chosen
Indicates a relationship where a model or system is responsible for organizing, storing, modifying, or otherwise managing files and their associated operations.
-
C.
fileManager
Indicates a relationship where an entity manages, organizes, or controls access to files or file-related operations for another entity.
-
D.
filingMethod
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
-
E.
fieldsPerFrame
Indicates the number of discrete fields that compose each video frame in an interlaced video signal.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5971f448819090f6e76c7d3ffc2d |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.