Triple
T12176882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2317.TW |
E290110
|
entity |
| Predicate | regionOfBusinessFocus |
P29376
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [2317.TW, regionOfBusinessFocus, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfBusinessFocus Context triple: [2317.TW, regionOfBusinessFocus, global]
-
A.
notableRegionOfBusiness
chosen
Indicates that a specified geographic region is a significant or primary area in which an entity conducts its business activities.
-
B.
primaryBusinessArea
Indicates the main field, sector, or domain in which an entity primarily conducts its business activities.
-
C.
underlyingCompanyBusinessFocus
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
D.
businessModelFocus
Indicates that one entity’s business model is centered on, tailored to, or primarily oriented around another entity or specific focus area.
-
E.
organizationFocus
Indicates the primary area of activity, mission, or specialization that an organization is oriented toward or concentrated on.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.