Triple
T28354254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VP9SK |
E718180
|
entity |
| Predicate | gripTexture |
P4016
|
FINISHED |
| Object | aggressive texturing for control |
—
|
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: aggressive texturing for control | Statement: [VP9SK, gripTexture, aggressive texturing for control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gripTexture Context triple: [VP9SK, gripTexture, aggressive texturing for control]
-
A.
gripFeature
Indicates that one entity has a specific grip-related characteristic or functionality in relation to another entity.
-
B.
gripType
Indicates the manner or style in which one entity physically holds or grasps another.
-
C.
gripRule
Indicates a rule or constraint governing how something may be gripped, held, or grasped.
-
D.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
-
E.
texture
chosen
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c2ad8648190a840aeb28c5bfd40 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:48 a.m.