Triple
T4600079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyISAM storage engine |
E100301
|
entity |
| Predicate | storesIndexesIn |
P57371
|
FINISHED |
| Object | .MYI files |
—
|
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: .MYI files | Statement: [MyISAM storage engine, storesIndexesIn, .MYI files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesIndexesIn Context triple: [MyISAM storage engine, storesIndexesIn, .MYI files]
-
A.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
B.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
C.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
D.
reportedlyStores
Indicates that an entity is said or believed, based on reports or claims, to store or hold another entity, without confirming that this storage actually occurs.
-
E.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.