Triple
T35667548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōkai region |
E1030613
|
entity |
| Predicate | majorCompanyBase |
P117996
|
FINISHED |
| Object | Toyota Motor 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: Toyota Motor Corporation | Statement: [Tōkai region, majorCompanyBase, Toyota Motor Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCompanyBase Context triple: [Tōkai region, majorCompanyBase, Toyota Motor Corporation]
-
A.
majorCompanyHeadquartered
Indicates that a company is a primary or significant corporate entity whose main headquarters is located in a specified place.
-
B.
majorCompanyLocatedIn
chosen
Indicates that a major company has its primary presence or headquarters in a specified location.
-
C.
主な企業
Indicates that an entity is a main or principal company associated with another entity or context.
-
D.
usedByCompanyHeadquarteredIn
Indicates that something (such as a product, service, or technology) is utilized by a company whose main headquarters is located in a specified place.
-
E.
isMajorCompanyIn
Indicates that a company is a leading or dominant business entity within a specified country, region, or market.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 3, 2026, 4:05 p.m.