Triple
T33205539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samsung Bioepis |
E850006
|
entity |
| Predicate | hasResearchAndDevelopmentCenterIn |
P11730
|
FINISHED |
| Object | Incheon |
E27787
|
NE 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: Incheon | Statement: [Samsung Bioepis, hasResearchAndDevelopmentCenterIn, Incheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchAndDevelopmentCenterIn Context triple: [Samsung Bioepis, hasResearchAndDevelopmentCenterIn, Incheon]
-
A.
hasResearchCentersIn
chosen
Indicates that an entity maintains or operates research centers located within a specified place or region.
-
B.
hasHeadquartersBuildingIn
Indicates that an organization’s main headquarters building is physically located in a specified place.
-
C.
isTechnologicalHubOf
Indicates that a location serves as a central focal point for technological activity, development, or innovation for another specified area or community.
-
D.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
E.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
- F. None of above.
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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0358c946f08190a8fb41c643074475 |
completed | May 12, 2026, 4:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a47823b95e0819090f4c8e7ad9b5998 |
completed | July 3, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a03586e5bb08190a71e075fde7cd679 |
completed | May 12, 2026, 4:42 p.m. |
Created at: May 1, 2026, 1:30 a.m.