Triple
T2481795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontiac Grand Am |
E55833
|
entity |
| Predicate | classChange |
P33367
|
FINISHED |
| Object | compact car to mid-size car over its production run |
—
|
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: compact car to mid-size car over its production run | Statement: [Pontiac Grand Am, classChange, compact car to mid-size car over its production run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classChange Context triple: [Pontiac Grand Am, classChange, compact car to mid-size car over its production run]
-
A.
classificationChange
chosen
Indicates a change in the category, type, or status under which an entity is classified.
-
B.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
C.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
D.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.