Triple
T34305125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States automotive market |
E880284
|
entity |
| Predicate | hasMajorManufacturer |
P52254
|
FINISHED |
| Object | General Motors |
—
|
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: General Motors | Statement: [United States automotive market, hasMajorManufacturer, General Motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorManufacturer Context triple: [United States automotive market, hasMajorManufacturer, General Motors]
-
A.
hasMajorCompanyOrigin
Indicates that an entity originates from, was founded by, or initially developed within a major company.
-
B.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
C.
hasMajorOrganization
Indicates that an entity is associated with or primarily represented by a major organization.
-
D.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
E.
hasUnderlyingCompanyIsMajorAutomaker
chosen
Indicates that the underlying company involved in the relationship is a major automobile manufacturer.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
Created at: May 1, 2026, 1:57 a.m.