Triple
T33105613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nichia Europe |
E847180
|
entity |
| Predicate | countryMarketScope |
P12320
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Nichia Europe, countryMarketScope, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryMarketScope Context triple: [Nichia Europe, countryMarketScope, European Union]
-
A.
marketRegion
chosen
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
B.
countryTargeted
Indicates that a particular country is the intended object or focus of an action, operation, or influence.
-
C.
countryScope
Indicates that something is limited to, applicable within, or defined at the level of a specific country.
-
D.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
E.
countryOrRegion
Indicates that one entity is a country or geographic region associated with another entity (such as its location, jurisdiction, or area of relevance).
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 1, 2026, 1:26 a.m.