Triple
T34849186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors |
E1004553
|
entity |
| Predicate | majorSupplier |
P22771
|
FINISHED |
| Object | Fisher Body Company |
—
|
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: Fisher Body Company | Statement: [General Motors, majorSupplier, Fisher Body Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSupplier Context triple: [General Motors, majorSupplier, Fisher Body Company]
-
A.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
B.
majorVendor
chosen
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
C.
supplierType
Indicates the classification or category of a supplier based on its role or characteristics in a supply relationship.
-
D.
majorSubcontractor
Indicates that one entity serves as a primary subcontractor responsible for significant portions of work under a contract with another entity.
-
E.
majorThirdParty
Indicates that an entity plays a significant but not primary role in a relationship, transaction, or situation involving other main parties.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4 p.m.