Triple
T31363159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPCA car factory |
E799933
|
entity |
| Predicate | hasSupplierNetworkType |
P197662
|
FINISHED |
| Object | automotive parts suppliers |
—
|
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: automotive parts suppliers | Statement: [TPCA car factory, hasSupplierNetworkType, automotive parts suppliers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupplierNetworkType Context triple: [TPCA car factory, hasSupplierNetworkType, automotive parts suppliers]
-
A.
hasDistributionNetworkServiceProvider
Indicates that an entity is associated with or utilizes a specific service provider responsible for operating or managing its distribution network.
-
B.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
-
C.
providesNetworkType
Indicates that one entity supplies or specifies the type of network associated with another entity.
-
D.
hasGlobalNetworkType
Indicates that an entity is associated with a specific type or category of global network.
-
E.
hasNetworkBrand
Indicates that one entity is associated with or operates under the network brand specified by another entity.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: April 29, 2026, 9:18 p.m.