Triple
T31019777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stridex |
E790420
|
entity |
| Predicate | appliedWith |
P196153
|
FINISHED |
| Object | pre-soaked pads |
—
|
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: pre-soaked pads | Statement: [Stridex, appliedWith, pre-soaked pads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedWith Context triple: [Stridex, appliedWith, pre-soaked pads]
-
A.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
B.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
C.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
D.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
E.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 29, 2026, 8:58 p.m.