Triple
T29564752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLP |
E753133
|
entity |
| Predicate | usedInCode |
P178967
|
FINISHED |
| Object | MX-SLP |
—
|
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: MX-SLP | Statement: [SLP, usedInCode, MX-SLP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCode Context triple: [SLP, usedInCode, MX-SLP]
-
A.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
B.
codeUsedBy
chosen
Indicates that a specific piece of code is utilized or depended upon by another entity (such as a system, application, or component).
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
E.
usedInSources
Indicates that something is referenced, applied, or employed within one or more information sources.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 28, 2026, 5:51 p.m.