Triple
T136017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden |
E2747
|
entity |
| Predicate | ownerType |
P4383
|
FINISHED |
| Object | multinational corporation subsidiary |
—
|
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: multinational corporation subsidiary | Statement: [Holden, ownerType, multinational corporation subsidiary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerType Context triple: [Holden, ownerType, multinational corporation subsidiary]
-
A.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
B.
organizationType
Indicates the specific category or classification of an organization in terms of its nature, structure, or primary function.
-
C.
parentOrganizationType
chosen
Indicates the classification or category of the organization that serves as the parent in a hierarchical relationship.
-
D.
sponsorType
Indicates the specific role or category of sponsorship that an entity provides in relation to another entity or event.
-
E.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25651b9048190a6277b7fec98c1ea |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.