Triple
T33922541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ube |
E869652
|
entity |
| Predicate | majorCompanyBasedIn |
P117996
|
FINISHED |
| Object | UBE Corporation |
—
|
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: UBE Corporation | Statement: [Ube, majorCompanyBasedIn, UBE Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCompanyBasedIn Context triple: [Ube, majorCompanyBasedIn, UBE Corporation]
-
A.
majorCompanyLocatedIn
chosen
Indicates that a major company has its primary presence or headquarters in a specified location.
-
B.
majorCompanyHeadquartered
Indicates that a company is a primary or significant corporate entity whose main headquarters is located in a specified place.
-
C.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
D.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
-
E.
notableCompanyFoundedIn
Indicates that a company is recognized as notable and was founded in the specified location or time period.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:49 a.m.