Triple
T5257287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Ramos Arizpe Assembly |
E118731
|
entity |
| Predicate | hasSecondaryActivity |
P26091
|
FINISHED |
| Object | component manufacturing |
—
|
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: component manufacturing | Statement: [GM Ramos Arizpe Assembly, hasSecondaryActivity, component manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryActivity Context triple: [GM Ramos Arizpe Assembly, hasSecondaryActivity, component manufacturing]
-
A.
secondaryActivity
chosen
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
B.
hasSecondarySubject
Indicates that an entity is associated with an additional, non-primary subject in a given context or relationship.
-
C.
hasSecondaryMeeting
Indicates that an entity is associated with an additional, follow-up, or subordinate meeting beyond a primary one.
-
D.
hasSecondaryFocus
Indicates that an entity has an additional, subordinate area of attention, concern, or specialization beyond its primary focus.
-
E.
hasSecondaryCore
Indicates that an entity possesses an additional, subordinate core component alongside its primary core.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.