Triple
T24862114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRT |
E622179
|
entity |
| Predicate | notableJeepModel |
P65462
|
FINISHED |
| Object | Jeep Grand Cherokee SRT |
—
|
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: Jeep Grand Cherokee SRT | Statement: [SRT, notableJeepModel, Jeep Grand Cherokee SRT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableJeepModel Context triple: [SRT, notableJeepModel, Jeep Grand Cherokee SRT]
-
A.
notableModelFamily
chosen
Indicates that one entity is a prominent or widely recognized model family associated with, produced by, or otherwise notably linked to another entity.
-
B.
notableCar
Indicates that the subject is a car recognized for its significance, prominence, or special interest (e.g., historically, culturally, or technically).
-
C.
carModel
Indicates the specific model designation of a car within a particular make or brand.
-
D.
notableElectricVariant
Indicates that one entity is a notable or significant electric-powered version or variant of another entity.
-
E.
usedVehicleModel
Indicates that a vehicle is a pre-owned (used) instance of a particular vehicle model.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 18, 2026, 5:22 a.m.