Triple
T11028256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BJ |
E260687
|
entity |
| Predicate | underlyingCompanyCustomerType |
P97362
|
FINISHED |
| Object | members |
—
|
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: members | Statement: [BJ, underlyingCompanyCustomerType, members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyCustomerType Context triple: [BJ, underlyingCompanyCustomerType, members]
-
A.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
-
B.
issuerCustomerType
Indicates the type or category of customer associated with or defined by the issuer.
-
C.
hasUnderlyingCompanyEmployeeType
Indicates that an entity is associated with a specific type or category of company employee that underlies or characterizes its role or status.
-
D.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
E.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797d245a0819085135cdee9b256c5 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.