Triple
T10502692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABT |
E247709
|
entity |
| Predicate | associatedCompanyBusinessArea |
P88259
|
FINISHED |
| Object | Medical devices |
—
|
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: Medical devices | Statement: [ABT, associatedCompanyBusinessArea, Medical devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyBusinessArea Context triple: [ABT, associatedCompanyBusinessArea, Medical devices]
-
A.
hasAssociatedCompany
Indicates that one entity is linked or connected to a company in an associated or affiliated manner.
-
B.
isPartOfBusinessArea
chosen
Indicates that one entity belongs to, is included within, or falls under the scope of a particular business area.
-
C.
associatedCompanySpecialization
Indicates that a company is linked to a particular area of specialization or expertise.
-
D.
memberCompany
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
E.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099c6a848190bf1d5361e9e61108 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.