Triple
T26473983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Thomas Assembly Plant |
E665975
|
entity |
| Predicate | hadBodyStyleFocus |
P160782
|
FINISHED |
| Object | full-size sedans |
—
|
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: full-size sedans | Statement: [St. Thomas Assembly Plant, hadBodyStyleFocus, full-size sedans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBodyStyleFocus Context triple: [St. Thomas Assembly Plant, hadBodyStyleFocus, full-size sedans]
-
A.
hadFocus
Indicates that an entity previously possessed or maintained primary attention, emphasis, or priority within a given context or interaction.
-
B.
oreBodyStyle
Indicates the specific body style or physical form that an ore or mineral deposit exhibits.
-
C.
lessFocusOn
Indicates that one entity directs reduced attention, emphasis, or priority toward another entity or activity compared to alternatives.
-
D.
awardingBodyFocus
Indicates the primary subject area or domain that an awarding body concentrates on when granting awards or qualifications.
-
E.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612cbbd188190bf01aede80ba1db5 |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 12:21 a.m.