Triple
T2312602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karabiner 98k |
E51991
|
entity |
| Predicate | slingConfiguration |
P29448
|
FINISHED |
| Object | side-mounted |
—
|
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: side-mounted | Statement: [Karabiner 98k, slingConfiguration, side-mounted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slingConfiguration Context triple: [Karabiner 98k, slingConfiguration, side-mounted]
-
A.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
B.
post2012Configuration
Indicates that an entity is arranged, structured, or operates according to the configuration or setup adopted after the year 2012.
-
C.
configurationLocation
Indicates the place or context where a configuration is stored, applied, or defined.
-
D.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
E.
directionalConfiguration
chosen
Indicates a specific spatial or directional arrangement that one entity has relative to another.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.