Triple
T15750828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabushiki gaisha |
E381838
|
entity |
| Predicate | companySuffixUsage |
P42400
|
FINISHED |
| Object | appears in Japanese company names |
—
|
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: appears in Japanese company names | Statement: [Kabushiki gaisha, companySuffixUsage, appears in Japanese company names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companySuffixUsage Context triple: [Kabushiki gaisha, companySuffixUsage, appears in Japanese company names]
-
A.
registrationSuffix
Indicates the trailing part or extension added to a base registration identifier to form a complete registration code.
-
B.
usedAsSuffixTo
chosen
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
C.
companyFullName
Indicates that the relationship specifies the complete, official legal name of a company.
-
D.
hasCompanyName
Indicates that an entity is associated with or identified by a specific company name.
-
E.
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.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.