Triple
T12674037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance Healthcare |
E302757
|
entity |
| Predicate | hasDistributionCenters |
P106228
|
FINISHED |
| Object | multiple European countries |
—
|
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: multiple European countries | Statement: [Alliance Healthcare, hasDistributionCenters, multiple European countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistributionCenters Context triple: [Alliance Healthcare, hasDistributionCenters, multiple European countries]
-
A.
numberOfDistributionCenters
Indicates the quantity of distribution centers associated with a given entity.
-
B.
isDistributedThrough
Indicates that something is supplied, circulated, or made available to others via a particular channel, medium, or distribution mechanism.
-
C.
hasNumberOfCentres
Indicates the relationship specifying how many centers (or central units/locations) are associated with a given entity.
-
D.
hasRetailStores
Indicates that an entity operates or possesses one or more physical retail store locations.
-
E.
hasDistributionPartners
Indicates that an entity collaborates with other entities to distribute its products or services.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961af991c8190b6079cb57e593b8f |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.