Triple
T21401652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PronoKal |
E527925
|
entity |
| Predicate | positionedIn |
P91855
|
FINISHED |
| Object | clinical weight-management market |
—
|
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: clinical weight-management market | Statement: [PronoKal, positionedIn, clinical weight-management market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedIn Context triple: [PronoKal, positionedIn, clinical weight-management market]
-
A.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
B.
locationPosed
chosen
Indicates that an entity is positioned or situated at a specific location.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionIncluded
Indicates that one position or spatial region is entirely contained within another position or spatial region.
-
E.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1702b44819080b282c22d151c88 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:18 p.m.