Triple
T33988660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boehringer Ingelheim |
E871479
|
entity |
| Predicate | hasManufacturingSiteIn |
P127653
|
FINISHED |
| Object | Germany |
—
|
NE NERFINISHED |
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: Germany | Statement: [Boehringer Ingelheim, hasManufacturingSiteIn, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManufacturingSiteIn Context triple: [Boehringer Ingelheim, hasManufacturingSiteIn, Germany]
-
A.
manufacturingSite
Indicates the location or facility where a product is or was manufactured.
-
B.
hasProductionSiteType
Indicates that an entity has a production site characterized by a specific type or category of production facility.
-
C.
hasProductionFacilitiesIn
chosen
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
-
D.
mainManufacturingSite
Indicates the primary location where an entity’s products are manufactured or produced.
-
E.
hasIndustrialSiteIn
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:50 a.m.