Triple
T24626980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM PATAC K platform |
E609568
|
entity |
| Predicate | coDeveloperRelationship |
P6901
|
FINISHED |
| Object | GM–SAIC joint venture engineering center |
—
|
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: GM–SAIC joint venture engineering center | Statement: [GM PATAC K platform, coDeveloperRelationship, GM–SAIC joint venture engineering center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coDeveloperRelationship Context triple: [GM PATAC K platform, coDeveloperRelationship, GM–SAIC joint venture engineering center]
-
A.
coDeveloperOf
chosen
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
B.
hasDeveloperRelation
Indicates a relationship in which one entity serves as the developer, creator, or builder of another entity.
-
C.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
D.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
-
E.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.