Triple
T24862224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson North Assembly Plant |
E622181
|
entity |
| Predicate | servesBrandSegment |
P162977
|
FINISHED |
| Object | SUV segment |
—
|
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: SUV segment | Statement: [Jefferson North Assembly Plant, servesBrandSegment, SUV segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBrandSegment Context triple: [Jefferson North Assembly Plant, servesBrandSegment, SUV segment]
-
A.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
B.
hasRetailSegment
Indicates that an entity is associated with, operates within, or targets a specific retail market segment.
-
C.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
D.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
E.
majorSegmentOf
Indicates that one entity constitutes a principal or most significant part of another larger whole.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 18, 2026, 5:22 a.m.