Triple
T9001028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Life Insurance |
E215037
|
entity |
| Predicate | businessForm |
P85630
|
FINISHED |
| Object | stock company |
—
|
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: stock company | Statement: [Sony Life Insurance, businessForm, stock company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessForm Context triple: [Sony Life Insurance, businessForm, stock company]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
C.
businessPractice
Indicates a relationship where an entity engages in, follows, or is characterized by a particular method, procedure, or customary way of conducting business activities.
-
D.
businessName
Indicates that one entity is the official or recognized business name of another entity.
-
E.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
- F. None of above. chosen
Provenance (4 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.