Triple
T36643588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code Morphing Software |
E904643
|
entity |
| Predicate | storesTranslatedCodeIn |
P186222
|
FINISHED |
| Object | code cache |
—
|
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: code cache | Statement: [Code Morphing Software, storesTranslatedCodeIn, code cache]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesTranslatedCodeIn Context triple: [Code Morphing Software, storesTranslatedCodeIn, code cache]
-
A.
languageOfCodes
Indicates that a particular language is used for or associated with a given set of codes.
-
B.
translationSource
Indicates that one entity serves as the original text or content from which another entity is translated.
-
C.
usedToTranslate
Indicates that one entity served as the tool, method, or medium for translating another entity from one language or representation to another.
-
D.
translationMethod
Indicates the technique or process used to translate content from one language or form to another.
-
E.
recordTranslatedBy
Indicates that a record has been translated by a particular agent or entity responsible for producing its translated version.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.