Triple
T19992779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exelon Patch |
E494103
|
entity |
| Predicate | applicationSite |
P138254
|
FINISHED |
| Object | upper back |
—
|
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: upper back | Statement: [Exelon Patch, applicationSite, upper back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationSite Context triple: [Exelon Patch, applicationSite, upper back]
-
A.
website
Indicates that one entity is the official website or web presence associated with another entity.
-
B.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
C.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
D.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
E.
typeSite
Indicates that a site is classified as being of a particular type or category.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe10ffc81908c94168b0a8ea9c9 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:31 p.m.