Triple
T33687733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangere |
E863086
|
entity |
| Predicate | basicSense |
P177195
|
FINISHED |
| Object | to touch physically |
—
|
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: to touch physically | Statement: [Tangere, basicSense, to touch physically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basicSense Context triple: [Tangere, basicSense, to touch physically]
-
A.
primarySense
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
B.
enhancedSense
Indicates that an entity possesses a heightened or improved sensory ability compared to a normal or baseline level.
-
C.
senses
Indicates that an entity perceives or detects another entity or stimulus through one of its senses.
-
D.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
E.
sensoryModality
Indicates the type of sensory channel (e.g., visual, auditory, tactile) through which an experience, perception, or information is received or processed.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.